Hi,

You can test it rather easily by yourself.

1)      Make a new WMS store by using URL 
http://demo.opengeo.org/geoserver/wms?service=wms&version=1.3.0&request=getcapabilities

2)      Publish some layer from the service

3)      Set the logging level of your Geoserver into Verbose logging

4)      Browse you new cascaded layer with the layer preview

5)      Look at the logs

I can see from my logs that the layer preview application sends WMS 1.1.0 
requests to my local Geoserver and it is forwarding the requests as

2015-08-13 17:21:40,544 DEBUG [data.ows] - Executed request to URL: 
http://demo.opengeo.org:80/geoserver/ows?SERVICE=WMS&LAYERS=ne%3Ane_10m_populated_places&CRS=EPSG:4326&FORMAT=image%2Fpng&HEIGHT=368&TRANSPARENT=TRUE&REQUEST=GetMap&WIDTH=768&BBOX=-11.83572284049336,-16.978337647899394,4.336152159506639,16.771662352100606&STYLES=&VERSION=1.3.0

The answer to your question is Yes.
I made my test with Geoserver 2.7.1.

-Jukka Rahkonen-


Joel Harris wrote:

Hello list,
I'm cascading a remote WMS as you may have guessed and the service I'm 
cascading supports WMS 1.3.0. I'm trying to utilize a stand alone Geowebcache 
(GWC) instance to cache the service cascaded by the Geoserver but GWC only 
supports WMS 1.1.1. I expected geoserver to make the translation of the request 
between 1.1.1 to 1.3.0, but it doesn't seem to accomplish this.
Is cascaded WMS supposed to support the interpretation between WMS versions?
trying this on Geoserver 2.5 and 2.7.1 with geowebcache 1.6 and 1.7.1 both 
stand-alone.
I'm running these instances on Glassfish 4.0, with java 1.7u71.
Thanks,
Joel
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to