On 18/12/2009 09:36, André Warnier wrote: > Christopher Schultz wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Abid, >> >> On 12/17/2009 12:08 PM, Abid Hussain wrote: >>> I used the startup parameters >>> -Duser.language=en >>> -Duser.region=US >>> This caused Tomcat to deliver the Last-Modified in the correct format. >>> >>> That solved the problem, no 404 anymore, thanks. >>> So it seems to be a bug in tomcat...? >> >> I would say so. >> >> http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.3.1 >> >> Tomcat's behavior seems to ignore the specification, here. Would you >> care to share your Tomcat version with us?
So far, I haven't seen anything that demonstrates Tomcat is generating this header. It looks like an app issue to me. My testing with trunk, 6.0.x and 6.0.20 all show the correct format being used. > I think that once this is confirmed, it may be worth raising its > visibility a bit for the Tomcat developers. As always before reporting an error, I'd highly recommend generating a simple as possible test case that demonstrates the issue on a clean Tomcat install. I can't repeat this and at the moment it looks like an application issue. Any bug report that can't be repeated is just going to get closed as WORKSFORME. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
