Hi All,
I have a client that uses the WMS/WMTS Cascade functionality a lot, but there has been an error when adding some geoservice addresses.
From what I’ve already investigated, the problem is that the geoserver expects the http response header to be capitalized, as is the standard http/1
But some new gis servers write it all tiny, as is the default on http/2
So… the geoserver cannot identify this response header, and returns an error.
Has anyone been through this, and knows how to solve it on GeoServer?
···
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
https://www.linkedin.com/in/fernandoquadro/
Please raise a ticket for the issue and I will try to take a look at it when I get a chance.
Ian
On Mon, 1 Nov 2021, 19:09 Fernando Quadro, <fsquadro@anonymised.com> wrote:
Hi All,
I have a client that uses the WMS/WMTS Cascade functionality a lot, but there has been an error when adding some geoservice addresses.
From what I’ve already investigated, the problem is that the geoserver expects the http response header to be capitalized, as is the standard http/1
But some new gis servers write it all tiny, as is the default on http/2
So… the geoserver cannot identify this response header, and returns an error.
Has anyone been through this, and knows how to solve it on GeoServer?
Best regards,
Fernando Quadro
http://www.fernandoquadro.com.br
https://www.linkedin.com/in/fernandoquadro/
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users