Bug #17098 Updated: apache sending 304 - not modified header

From: Date: Wed, 10 Jul 2002 17:37:45 +0000
Subject: Bug #17098 Updated: apache sending 304 - not modified header
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-13753@lists.php.net to get a copy of this message
 ID:               17098
 Updated by:       pmoor@netpeople.ch
 Reported By:      pmoor@netpeople.ch
 Status:           Feedback
 Bug Type:         Apache2 related
 Operating System: custom linux
 PHP Version:      4.0CVS-2002-05-08
 New Comment:

however: it doesn't work for phpmyadmin ( still displaying old query
results ), BUT at least one of my regular scripts ( just some simple
task ) does indeed work: apache's returning the expected 200 OK
response.


Previous Comments:
------------------------------------------------------------------------

[2002-07-10 13:31:43] pmoor@netpeople.ch

still doesn't work with php4 and apache2 checkouts from July 10th.

------------------------------------------------------------------------

[2002-07-07 21:10:22] sniper@php.net

Does this happen with latest CVS checkouts of both Apache2 and PHP?


------------------------------------------------------------------------

[2002-06-07 16:25:47] ck-phpbugs@newsclub.de

See Apache2 bug #9673
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9673

Same problem here, seems to be a problem with Apache2 and the filter
concept.

You can have a quick workaround for the moment -
just comment out the If-Modified-Since handling stuff in Apache2:

Comment out line 393 in modules/http/http_protocol.c, (return
HTTP_NOT_MODIFIED). Now, Apache2 does never return 304 Not modified.

And hey, this is a preliminary hot fix only!

Please also check the suggestions of Justin Erenkrantz (see Apache bug
report), I haven't had the time yet to do so.

------------------------------------------------------------------------

[2002-05-21 17:05:45] info@tphnet.com

Same problem here. You can easily test it by taking one of your php
files and removing a ';' somewhere. Load the page in the browser and
you'll see an error. Correct the error in the php file and reload the
page in you browser. You still get the same error. Manually clearing
the browser cache is (as far as i have tested) the only solution.
Strange thing is, that when i use PHPmyAdmin, dynamic pages aren't
updated (403 not modified). But when I use some of my own script,
dynamic pages do get updated. They only get stuck in the cache if I
edit the php file itself (as described above).

Running Apache 2.0.35 and PHP 4.2.0 on Windows NT 5.1. The same install
of PHP running on Apache 1.3.24 doesn't give any problems.

------------------------------------------------------------------------

[2002-05-08 10:36:01] pmoor@netpeople.ch

using phpmyadmin with apache 2.0.35 and php4.3-dev results in pages not
being reloaded, when once requested.

if i drop an entry in an mysql table, and re-list the table, the old
entry is still showing up (the browser is displaying the old page
instead of a reloaded one). this is, because apache sends a 304 nod
modified header. verified with mozilla-latest-1.0.0.

it worked great with apache 1.3.24 though...

------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=17098&edit=1



Thread (26 messages)

« previous php.bugs (#13753) next »