tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5486] - Standard EA3 Taglib import does not work with if-modified-since http header field
Date Thu, 20 Dec 2001 02:27:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5486>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5486

Standard EA3 Taglib import does not work with if-modified-since http header field

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From craig.mcclanahan@sun.com  2001-12-19 18:27 -------
After reading your bug report three times (and running the attached sample), I'm 
still a little dense.  I can repeatedly run your test client program, and 
repeatedly get exactly the same output data (with the line that says "This 
should be shown if working correctly") against the latest code in the HEAD 
branch of Tomcat 4 (i.e. what you'd get with nightly builds).

In particular, you did not state what is supposed to be different in the 
response, so it's not clear if I'm interpreting your report correctly.  
Therefore, I'm going to close this with WORKSFORME.  Feel free to reopen this if 
you can provide more info to help me understand what's going wrong from your 
perspective.

You will note that every response from Tomcat includes a "Date" header.  If 
you've configured your browser to do so, it will use this date value in a 
subsequent "If-Modified-Since" header for the same request URI.  The fact that 
this seems to make a difference, and that the problem only happens to you in 
Opera, points to Opera's caching as a potential problem.

You could try configuring Netscape to send the If-Modified-Since header (it's 
controlled by the settings on the Advanced -> Cache page) and see if you can 
observe the same results.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message