WicketFilter always sets expires header to 1h for shared resources if browser sends if-modified-since header

2011-09-05 Thread Thomas Heigl
always sets the expiry header to 1 hour if the browser sends a request including an IF-MODIFIED-SINCE-header. The relevant code is in WicketFilter (1.4.16) 347-350: httpServletResponse.setStatus(HttpServletResponse.SC_NOT_MODIFIED); httpServletResponse.setDateHeader(Expires

Re: WicketFilter always sets expires header to 1h for shared resources if browser sends if-modified-since header

2011-09-05 Thread Martin Grigorov
some debugging, I found out that Wicket always sets the expiry header to 1 hour if the browser sends a request including an IF-MODIFIED-SINCE-header. The relevant code is in WicketFilter (1.4.16) 347-350:    httpServletResponse.setStatus(HttpServletResponse.SC_NOT_MODIFIED

Re: WicketFilter always sets expires header to 1h for shared resources if browser sends if-modified-since header

2011-09-05 Thread Thomas Heigl
always sets the expiry header to 1 hour if the browser sends a request including an IF-MODIFIED-SINCE-header. The relevant code is in WicketFilter (1.4.16) 347-350: httpServletResponse.setStatus(HttpServletResponse.SC_NOT_MODIFIED); httpServletResponse.setDateHeader(Expires

Re: WicketFilter always sets expires header to 1h for shared resources if browser sends if-modified-since header

2011-09-05 Thread Martin Grigorov
-SINCE-header. The relevant code is in WicketFilter (1.4.16) 347-350:    httpServletResponse.setStatus(HttpServletResponse.SC_NOT_MODIFIED);    httpServletResponse.setDateHeader(Expires, System.currentTimeMillis() + Duration.hours(1).getMilliseconds()); There already is an issue

Re: If-Modified-Since header

2010-11-03 Thread Mauro Ciancio
and according to the parameters I serve differents photos. Once the photos are uploaded they never change, so I'd like the photos be cached. I'm expecting to get a 304 not modified, but the If-Modified-Since header is ignored because of the mount path is not under '/resources'. Is this clearer? Should

Re: If-Modified-Since header

2010-10-31 Thread Martin Grigorov
by the web container Take a look at http://code.google.com/p/wro4j/ On Sun, Oct 31, 2010 at 1:11 AM, Mauro Ciancio maurocian...@gmail.comwrote: Hello everyone: I've been trying to get properly working the caching in my site's resources using the if-modified-since header. I've noticed that the check

Re: If-Modified-Since header

2010-10-31 Thread Mauro Ciancio
wanted. My resources gets mounted at domain.com/photos/my/parameters and according to the parameters I serve differents photos. Once the photos are uploaded they never change, so I'd like the photos be cached. I'm expecting to get a 304 not modified, but the If-Modified-Since header is ignored because

If-Modified-Since header

2010-10-30 Thread Mauro Ciancio
Hello everyone: I've been trying to get properly working the caching in my site's resources using the if-modified-since header. I've noticed that the check for the header is only done if the resource is mounted under the '/resources' url (wicket filter @ line 1130, Wicket 1.4). My resources