https://issues.apache.org/bugzilla/show_bug.cgi?id=55228
Mark Thomas ma...@apache.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.apache.org/bugzilla/show_bug.cgi?id=55228
--- Comment #5 from Mark Thomas ma...@apache.org ---
Fair enough.
This has been fixed for trunk and 7.0.x and will be included in 7.0.43 onwards.
The fix has been proposed for 6.0.x.
--
You are receiving this mail because:
You are the
https://issues.apache.org/bugzilla/show_bug.cgi?id=55228
--- Comment #2 from Mark Thomas ma...@apache.org ---
If a bug affects multiple versions open an issue (as you have done) against the
earliest supported version you want to see the fix in. Fixes are applied to
trunk and then back-ported
https://issues.apache.org/bugzilla/show_bug.cgi?id=55228
--- Comment #3 from Mark Thomas ma...@apache.org ---
I'm currently leaning to resolving this as invalid. As an origin server, Tomcat
is required by RFc2616 to set the date header (using the current time) on every
request.
I'd be prepared
https://issues.apache.org/bugzilla/show_bug.cgi?id=55228
--- Comment #1 from f...@alum.mit.edu f...@alum.mit.edu ---
I opened this bug against Tomcat6 since that is what we're using, but this bug
exists on all Tomcat7, as well, and most likely Tomcat8. I'm not sure how to
deal with that.
https://issues.apache.org/bugzilla/show_bug.cgi?id=55228
f...@alum.mit.edu f...@alum.mit.edu changed:
What|Removed |Added
CC|
