#17098 [Com]: apache sending 304 - not modified header

From: Date: Thu, 09 Jan 2003 20:45:39 +0000
Subject: #17098 [Com]: apache sending 304 - not modified header
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-29606@lists.php.net to get a copy of this message
 ID:               17098
 Comment by:       daniel.eckl@gmx.de
 Reported By:      pmoor@netpeople.ch
 Status:           Closed
 Bug Type:         Apache2 related
 Operating System: linux
 PHP Version:      4.0CVS-2002-10-17
 New Comment:

I tried this and tested it with Horde's IMP which heavily needs correct
caching behavior. So far it seems to behave very smoothly. I'm
impressed of this idea.

I took some time but couldn't think of any drawbacks caused by this.
Because the unsetting is only internal, there should be no problems
with search spiders etc...

Any other opinions?

Greets,
Daniel


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

[2003-01-03 13:44:12] pmichaud@pobox.com

As another possible temporary workaround, I tried adding the directive

   RequestHeader unset If-Modified-Since

into my Apache configuration when processing PHP scripts.  This removes
the If-Modified-Since header entirely, causing Apache to always return
a 200 response.  The resulting configuration looks like:

<Files *.php>
    SetOutputFilter PHP
    SetInputFilter PHP
    LimitRequestBody 524288
    RequestHeader unset If-Modified-Since
</Files>

Anyone know of a reason why this might be bad or otherwise won't work?

Pm

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

[2002-12-29 15:56:05] derick@php.net

Try a NON stable snapshot, it's fixed in CVS>

Derick

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

[2002-12-29 15:51:59] dk@webcluster.at

Isn't fixed in php4-STABLE-200212290030

Daniel [datenPUNK] Khan

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

[2002-12-27 14:13:19] iliaa@php.net

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.



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

[2002-12-27 13:55:15] daniel.eckl@gmx.de

... and the bug is present in 4.3.0 release.

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

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/17098

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



Thread (26 messages)

« previous php.bugs (#29606) next »