*wicket setting the wrong "Expires" header this is for the http response headers
sorry for the confusion On Fri, Nov 19, 2010 at 1:04 AM, Carlo Camerino <[email protected]>wrote: > Hi, > > I seem to be ahving a problem with wicket settings the wrong expires > header. > > It keeps on setting an expires header that is around 7 hours before the > actual time that i'm trying to test it. > This causes glassfish not to cache properly. > > > Expires Thu, 18 Nov 2010 15:00:30 GMT > Content-Type application/x-javascript > Cache-Control max-age=3600 > Last-Modified Thu, 08 Jul 2010 03:45:53 GMT > Content-Encoding gzip > Content-Length 46116 > Server Jetty(6.1.15) > > Is there any way that I can prevent wicket from settings the expires header > and the cache control? > > I'd rather control it from my own filter which sets these things. > Problem is, wicket keeps on overriding whatever i set. > > > THanks A Lot > > hopoing to get help on this one. >
