You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/06/04 23:14:58 UTC

DO NOT REPLY [Bug 20475] - Page delay and 304 error after modification

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=20475>.
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=20475

Page delay and 304 error after modification

slive@apache.org changed:

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



------- Additional Comments From slive@apache.org  2003-06-04 21:14 -------
304 is not an error; it means "page not modified".  It is returned only if
the client uses an "if-modified-since" request header.  The client should then
use its cached version of the page.

Hence this must be a client problem.  Either it doesn't have the page cached,
in which case it shouldn't be sending "if-modified-since" or it does, in 
which case it should return the cached version.

I have no idea what exactly is triggering this.  If you would like to discuss
it further, I suggest providing more details on your setup with a posting to
the users@httpd.apache.org mailing list.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org