Kevin and Jukka and all,
First off, if you want to use the standard GeoServer WMS endpoint with
caching, you need to make sure that you have Direct Integration enabled.
Yeps, it is enabled.
Second, you need to make sure the layer is configured for caching and that
you have set it up with the correct format, gridset, parameter filters, et
to handle your request. If anything doesn't match, it will fall back to
using GeoServer's WMS service directly without any caching.
Should be. Declared SRS is EPSG:3067 and on Openlayers I use EPSG:900913.
OpenLayers isn't able to read the gridset information from a WMS-C
GetCapabilities document so if you give it a layer using a custom gridset
it will simply guess how the tiles are laid out and make requests on that
basis. If it guesses wrong, then the requests won't line up with the cache
and GWC won't be able to handle it. If you're using GWC directly you'll
get an error, while if you're using the regular GeoServer WMS endpoint with
Direct Integration enabled, it will fall back to using the WMS without
caching.
Yep. That's how I have understand it.
The GWC endpoints are /geoserver/gwc/service/wms
I must try this
In order to use any gridset other than the standard Web Mercator or WGS84
ones you have to tell OpenLayers the exact parameters of that gridset, at
least if you're using WMS-C.
I suppose, I use Mercator.
projection: mercator
I noticed one more thing more. When using this layer, there is maybe 5 different resolution. When draging tiles on levels 2-5, there is no caching, but on level 1 gwc is caching tiles?!
--kupen
--
Wippies-vallankumous on täällä! Varmista paikkasi vallankumouksen eturintamassa ja liity Wippiesiin heti!
http://www.wippies.com/
--
Wippies-vallankumous on täällä! Varmista paikkasi vallankumouksen eturintamassa ja liity Wippiesiin heti!
http://www.wippies.com/