hi all,
my webapp dynamically generates new SLDs that allways have the same name.
These new SLDs are used to get a new Legend.
As the names of the SLDs doesn't change, the path of GetLegend request in
the ...GetLegend?SLD=.../x.sld doesn't change and it seems to be here a
caching problem, as the NEW legend doesn't appear.
It seems as if the server needs to set the response cache headers so that
the client does not cache the resource.
Just wondering... can I do it by Geoserver or should I modify Tomcat config
files?
thanks,
Pere
--
View this message in context: http://www.nabble.com/not-caching-images...possible-setup-from-Geoserver--tp21604480p21604480.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
sorry, here I meant..."As the names of the SLDs doesn't change, the path
of GetLegend request in the img src="...GetLegend?SLD=.../x.sld".....
Pere
pere roca wrote:
hi all,
my webapp dynamically generates new SLDs that allways have the same name.
These new SLDs are used to get a new Legend.
As the names of the SLDs doesn't change, the path of GetLegend request in
the ...GetLegend?SLD=.../x.sld doesn't change and it seems to be here a
caching problem, as the NEW legend doesn't appear.
It seems as if the server needs to set the response cache headers so that
the client does not cache the resource.
Just wondering... can I do it by Geoserver or should I modify Tomcat
config files?
thanks,
Pere
--
View this message in context: http://www.nabble.com/not-caching-images...possible-setup-from-Geoserver--tp21604480p21604555.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi Pere,
I do not think GeoServer puts HTTP cache or expire information in the headers of these responses, so it's the default settings of your browser / client that apply.
You may be able to have Tomcat set these headers, if you proxy through Apache you can certainly do it. Or you can just have your client append a bogus parameter with a random value to the request string.
-Arne
pere roca wrote:
hi all,
my webapp dynamically generates new SLDs that allways have the same name.
These new SLDs are used to get a new Legend.
As the names of the SLDs doesn't change, the path of GetLegend request in
the ...GetLegend?SLD=.../x.sld doesn't change and it seems to be here a
caching problem, as the NEW legend doesn't appear.
It seems as if the server needs to set the response cache headers so that
the client does not cache the resource.
Just wondering... can I do it by Geoserver or should I modify Tomcat config
files?
thanks,
Pere
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Ah! I knew the trick of the random value but didn’t figure out it would work with a GetLegend Request (as they are standard)… but it works!
thanks!
Pere
2009/1/22 Arne Kepp <ak@anonymised.com.1671…>
Hi Pere,
I do not think GeoServer puts HTTP cache or expire information in the headers of these responses, so it’s the default settings of your browser / client that apply.
You may be able to have Tomcat set these headers, if you proxy through Apache you can certainly do it. Or you can just have your client append a bogus parameter with a random value to the request string.
-Arne
pere roca wrote:
hi all,
my webapp dynamically generates new SLDs that allways have the same name.
These new SLDs are used to get a new Legend.
As the names of the SLDs doesn’t change, the path of GetLegend request in
the …GetLegend?SLD=…/x.sld doesn’t change and it seems to be here a
caching problem, as the NEW legend doesn’t appear.
It seems as if the server needs to set the response cache headers so that
the client does not cache the resource.
Just wondering… can I do it by Geoserver or should I modify Tomcat config
files?
thanks,
Pere
–
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
–
Pere Roca Ristol
Biòleg i especialista GIS
Museo Nacional de Ciencias Naturales (CSIC)
Visita l’EDIT mapViewer!
http://edit.csic.es/edit_geo/prototype/edit.html