How to avoid Expires: 1970 header with URIRequestTargetUrlCodingStrategy

2007-11-27 Thread Edvin Syse
In my WicketApplication class I have mounted a URL with the URIRequestTargetUrlCodingStrategy to serve files in my virtualhosted CMS-application written in Wicket 1.3. The problem with this is that it returns a header like this with the file it serves up: HTTP/1.1 200 OK Expires: Thu, 01

Re: How to avoid Expires: 1970 header with URIRequestTargetUrlCodingStrategy

2007-11-27 Thread Johan Compagner
hmm this way i have never seen it before :) But you could also do this with a mounted shared resource But what you could do if you want to do it that way then overwrite the ResourceStreamRequestTargets: * protected* *void* configure(*final* RequestCycle requestCycle, *final*Response response,

Re: How to avoid Expires: 1970 header with URIRequestTargetUrlCodingStrategy

2007-11-27 Thread Edvin Syse
hmm this way i have never seen it before :) Hehe.. I know it might be a bit unconventional, but I think I have a good reason for it. Since the application is virtualhosted, the session holds a path to the filearchive for the current instance (set based on the http host of the request), and the

Re: How to avoid Expires: 1970 header with URIRequestTargetUrlCodingStrategy

2007-11-27 Thread Johan Compagner
No you don't have to hve the servlet response for that Just check if the Response is a WebResponse That already has the setHeader methods On Nov 27, 2007 9:13 PM, Edvin Syse [EMAIL PROTECTED] wrote: hmm this way i have never seen it before :) Hehe.. I know it might be a bit unconventional,

Re: How to avoid Expires: 1970 header with URIRequestTargetUrlCodingStrategy

2007-11-27 Thread Edvin Syse
No you don't have to hve the servlet response for that Just check if the Response is a WebResponse That already has the setHeader methods Thank you so much, it worked perfectly :) -- Edvin - To unsubscribe, e-mail: [EMAIL