[Geoserver-users] Trying to connect to a remote WMS that insists on lower case parameter names

Hi all,

I’m trying to setup geoserver (2.11.1) to cascade a remote WMS. When I attempt this I get an error:

Connection test failed: Server returned HTTP response code: 401 for URL: https://xxxx/wms?REQUEST=GetCapabilities&SERVICE=WMS…etc.

Turns out that the server I’m connecting to insists on lower case parameter names in the URL. I setup the Capabilities URL in the Connection Info configuration to use a URL with lower case parameter names. However the Connection test error (above) displays uppercase for all parameter names i.e. request=GetCapabilities gets shifted to REQUEST=GetCapabilities, which then gets rejected by the other end.

The long and the short of it…Is it true that geoserver makes uppercase the parameter names? If so, is it configurable not to do so?

Cheers,

Duncan

Hi Duncan,
the server is not compliant, the OGC specs state clearly that parameter keys are case insensitive,
in all protocols with KVP bindings (like WMS).

As a result, there is no way to control the parameters key case, because it’s not meant to matter
(that said, I guess it can be made so with some coding).

Cheers
Andrea

···

On Mon, Jul 31, 2017 at 9:23 AM, Duncan Sayers <duncansayers@anonymised.com> wrote:

Hi all,

I’m trying to setup geoserver (2.11.1) to cascade a remote WMS. When I attempt this I get an error:

Connection test failed: Server returned HTTP response code: 401 for URL: https://xxxx/wms?REQUEST=GetCapabilities&SERVICE=WMS…etc.

Turns out that the server I’m connecting to insists on lower case parameter names in the URL. I setup the Capabilities URL in the Connection Info configuration to use a URL with lower case parameter names. However the Connection test error (above) displays uppercase for all parameter names i.e. request=GetCapabilities gets shifted to REQUEST=GetCapabilities, which then gets rejected by the other end.

The long and the short of it…Is it true that geoserver makes uppercase the parameter names? If so, is it configurable not to do so?

Cheers,

Duncan


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Technically that means the server you are connecting to is not a WMS as the spec allows for any casing of the keys (though interestingly not the values), section 6.8.1. So please raise it as a bug with them about this.

On a more helpful note, yes GeoTools does use uppercase for key values but it would be a relatively easy thing to change in org.geotools.data.ows.AbstractRequest.setProperty. So it is worth raising a FeatureRequest or if this is urgent consider sponsoring the work.

Ian

···

On 31 July 2017 at 08:23, Duncan Sayers <duncansayers@anonymised.com> wrote:

Hi all,

I’m trying to setup geoserver (2.11.1) to cascade a remote WMS. When I attempt this I get an error:

Connection test failed: Server returned HTTP response code: 401 for URL: https://xxxx/wms?REQUEST=GetCapabilities&SERVICE=WMS…etc.

Turns out that the server I’m connecting to insists on lower case parameter names in the URL. I setup the Capabilities URL in the Connection Info configuration to use a URL with lower case parameter names. However the Connection test error (above) displays uppercase for all parameter names i.e. request=GetCapabilities gets shifted to REQUEST=GetCapabilities, which then gets rejected by the other end.

The long and the short of it…Is it true that geoserver makes uppercase the parameter names? If so, is it configurable not to do so?

Cheers,

Duncan


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Ian Turton

Yeah, I have pointed out to them that the server isn’t compliant. Think they might have put it in the too hard basket. Thanks Andrea…

Regards,

Duncan

···

On Mon, Jul 31, 2017 at 6:01 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi Duncan,
the server is not compliant, the OGC specs state clearly that parameter keys are case insensitive,
in all protocols with KVP bindings (like WMS).

As a result, there is no way to control the parameters key case, because it’s not meant to matter
(that said, I guess it can be made so with some coding).

Cheers
Andrea

On Mon, Jul 31, 2017 at 9:23 AM, Duncan Sayers <duncansayers@anonymised.com> wrote:

Hi all,

I’m trying to setup geoserver (2.11.1) to cascade a remote WMS. When I attempt this I get an error:

Connection test failed: Server returned HTTP response code: 401 for URL: https://xxxx/wms?REQUEST=GetCapabilities&SERVICE=WMS…etc.

Turns out that the server I’m connecting to insists on lower case parameter names in the URL. I setup the Capabilities URL in the Connection Info configuration to use a URL with lower case parameter names. However the Connection test error (above) displays uppercase for all parameter names i.e. request=GetCapabilities gets shifted to REQUEST=GetCapabilities, which then gets rejected by the other end.

The long and the short of it…Is it true that geoserver makes uppercase the parameter names? If so, is it configurable not to do so?

Cheers,

Duncan


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.