But is it then really downloaded? Because the brower makes first a head request to it and that will say not changed
On 5/8/08, Stefan Simik <[EMAIL PROTECTED]> wrote: > > Hi boys, > > I think, there is one problem with wicket ajax javascripts - there are > reloading by browser every > hour, because the Expire header is hardcoded to 3600 seconds in > WebResource#setHeaders() method. > > It is really needed to repeatedly once an hour download these wicket > javascripts ? > These are static wicket javascripts, they are not subject of changes, so > why could they not be cached for longer time, for example - 1 week, or > longer. > > It would be better, if caching time should be configurable from some > application settings. > Could I create requet for improvement, or it is all ok ? > > thx > Stefan Simik > > // > I have consulted this before, but without result. So now, I am trying to > show > the problem in a simpler situation. > > > -- > View this message in context: > http://www.nabble.com/Wicket-javascripts---reloading-every-one-hour-tp17117009p17117009.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
