[Geoserver-users] Config cascading WMS 1.3: Capabilities req params overruled

GeoServer GeoServer User
1

And the GetMap url in server GetCapabilities does not contain that &version=1.1.1 part?

-Jukka Rahkonen-

···

Lähettäjä: Edward Mac Gillavry [mailto:emacgillavry@anonymised.com]
Lähetetty: 4. syyskuuta 2014 16:48
Vastaanottaja: Andrea Aime; Rahkonen Jukka (Tike)
Kopio: Geoserver-users@lists.sourceforge.net
Aihe: RE: [Geoserver-users] Config cascading WMS 1.3: Capabilities req params overruled

Hi,

Thanks for your pointers. The upstream WMS server (SharpMap) ONLY supports WMS 1.3. Sending a proper, full GetCapabilities request version 1.3 to the upstream WMS server using wget or the web browser, I get the proper document in response.

The “client” here is GeoServer, as I am configuring the upstream WMS as a store in the GS management interface with the exact same GetCapabilities URL for version 1.3. Upon adding layers, GS appears to hijack the request tagging version 1.1.1 onto the end of the request.

No INSPIRE metadata is involved in the exchange.

Hope this makes it more clear.

Thanks in advance,

Edward

Date: Thu, 4 Sep 2014 15:25:04 +0200
Subject: Re: [Geoserver-users] Config cascading WMS 1.3: Capabilities req params overruled
From: andrea.aime@anonymised.com
To: jukka.rahkonen@anonymised.com
CC: emacgillavry@anonymised.com; geoserver-users@lists.sourceforge.net

On Thu, Sep 4, 2014 at 3:12 PM, Rahkonen Jukka (Tike) <jukka.rahkonen@anonymised.com> wrote:

Hi,

Please check what you get back from the remote server if you send a GetCapabilities request with &VERSION=1.3.0. I bet it is sending back a document in WMS 1.1.1 format because it does not support WMS 1.3.0. After that Geoserver continues discussion with the WFS 1.1.1 protocol. This is by design and build in into WMS standard. Read more about version negotiation from the WMS 1.3.0 standard, it begins from page 10.

It may also be that the client fails to deal with the 1.3.0 capabilities document returned, and falls back to 1.1.1.

I remember issues cascading servers exposing the INSPIRE extra metadata for example, that was solved at some point, but can’t exactly remember when

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit

http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

2

That’s right: the GetMap URL does not contain any reference to a version number, not even 1.1.1.

Edward

From: jukka.rahkonen@anonymised.com
To: emacgillavry@anonymised.com
CC: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Config cascading WMS 1.3: Capabilities req params overruled
Date: Thu, 4 Sep 2014 13:51:16 +0000

And the GetMap url in server GetCapabilities does not contain that &version=1.1.1 part?

-Jukka Rahkonen-

Lähettäjä: Edward Mac Gillavry [mailto:emacgillavry@anonymised.com]
Lähetetty: 4. syyskuuta 2014 16:48
Vastaanottaja: Andrea Aime; Rahkonen Jukka (Tike)
Kopio: Geoserver-users@lists.sourceforge.net
Aihe: RE: [Geoserver-users] Config cascading WMS 1.3: Capabilities req params overruled

Hi,

Thanks for your pointers. The upstream WMS server (SharpMap) ONLY supports WMS 1.3. Sending a proper, full GetCapabilities request version 1.3 to the upstream WMS server using wget or the web browser, I get the proper document in response.

The “client” here is GeoServer, as I am configuring the upstream WMS as a store in the GS management interface with the exact same GetCapabilities URL for version 1.3. Upon adding layers, GS appears to hijack the request tagging version 1.1.1 onto the end of the request.

No INSPIRE metadata is involved in the exchange.

Hope this makes it more clear.

Thanks in advance,

Edward

Date: Thu, 4 Sep 2014 15:25:04 +0200
Subject: Re: [Geoserver-users] Config cascading WMS 1.3: Capabilities req params overruled
From: andrea.aime@anonymised.com
To: jukka.rahkonen@anonymised.com
CC: emacgillavry@anonymised.com; geoserver-users@lists.sourceforge.net

On Thu, Sep 4, 2014 at 3:12 PM, Rahkonen Jukka (Tike) <jukka.rahkonen@anonymised.com> wrote:

Hi,

Please check what you get back from the remote server if you send a GetCapabilities request with &VERSION=1.3.0. I bet it is sending back a document in WMS 1.1.1 format because it does not support WMS 1.3.0. After that Geoserver continues discussion with the WFS 1.1.1 protocol. This is by design and build in into WMS standard. Read more about version negotiation from the WMS 1.3.0 standard, it begins from page 10.

It may also be that the client fails to deal with the 1.3.0 capabilities document returned, and falls back to 1.1.1.

I remember issues cascading servers exposing the INSPIRE extra metadata for example, that was solved at some point, but can’t exactly remember when

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit

http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it