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.
However, if my guess was wrong and the remote server supports WMS 1.3.0 then
there is something else going on and we need to get some more information. The
server URL would be best but I know that all servers are not public. By the
way, there is nothing better in WMS 1.3.0 than in 1.1.1 so if it works so just
use it.
-Jukka Rahkonen-
Edward Mac Gillavry wrote:
Dear all,
Configuring a cascading WMS, one has to provide Connection Info, for example
the Capabilities URL. Although I provide a full Capbilities URL to a WMS 1.3
service, the actual request sent to remote WMS has the string
"REQUEST=GetCapabilities&VERSION=1.1.1&SERVICE=WMS" tagged onto the end. This
effectively overrules the request supplied.
We're running GeoServer v.2.4.0. Any thoughts why this happens? Is this by
design?
Cheers,
Edward
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
