GWC ignores the layer http caching settings
-------------------------------------------
Key: GEOS-4760
URL: https://jira.codehaus.org/browse/GEOS-4760
Project: GeoServer
Issue Type: Bug
Components: GWC
Reporter: Andrea Aime
Assignee: Gabriel Roldán
A layer can be configured with a max-age http caching header.
GeoServer WMS honors it, but the embedded GWC does not:
results in:
{panel}
HTTP/1.1 200 OK
Date: Fri, 09 Sep 2011 10:17:06 GMT
Server: Apache
Set-Cookie: GS_FLOW_CONTROL="GS_CFLOW_37ae75f:1324d8693ff:-7ea7"; Version=1
Expires: Mon, 12 Sep 2011 10:17:06 GMT
Cache-Control: max-age=259200, must-revalidate
Content-Disposition: inline; filename=GeoSolutions-world.200405.jpg
Connection: close
Transfer-Encoding: chunked
Content-Type: image/jpeg
{panel}
while the
results in:
{panel}
HTTP/1.1 200 OK
Date: Fri, 09 Sep 2011 10:13:59 GMT
Server: Apache
geowebcache-tile-index: [1, 0, 0]
Content-Length: 10036
Connection: close
Content-Type: image/jpeg
{panel}
(Direct integration is disabled on that server as it's not working properly, the build is less than a month old, trunk)
I also see that the direct integration seems to set a etag as an alternative mean of preventing reloads, but that does not appear to be used by the direct GWC link.
In any case, a max-age header prevents the request at all, instead of replacing it with a quicker one, so imho GWC should try to respect the max-age header if set
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira