ID: 50276
User updated by: vector dot thorn at gmail dot com
Reported By: vector dot thorn at gmail dot com
Status: Bogus
Bug Type: Apache2 related
Operating System: Fedora Linux
PHP Version: 5.3.1
New Comment:
Thank you for the clarification.
Well in your documentation it states that "the header should replace a
previous similar header", so i thought that it was referring to all
output headers, whereas now i see that it is only other php headers. You
might want to flag that for clarification.
Previous Comments:
------------------------------------------------------------------------
[2009-11-25 09:17:32] j...@php.net
Thank you Carsten.
------------------------------------------------------------------------
[2009-11-25 07:28:07] carsten_sttgt at gmx dot de
| I expected it to send the proper cache headers,
| despite what the server was preconfigured to send.
No bug in PHP:
Header directives (mod_header) are processed just before the response
is sent to the network (and after any content generator like PHP).
--> and if you configure mod_header to remove e.g. Cache-Control
from the response headers, it's doing this....
Regards,
Carsten
------------------------------------------------------------------------
[2009-11-25 07:25:53] j...@php.net
This is propably just Apache issue, I can change any headers using
Fastcgi just fine.
------------------------------------------------------------------------
[2009-11-24 21:59:06] vector dot thorn at gmail dot com
Yes and no. PHP was not sending the headers that i specified, which
should have overwritten the default server headers. I had to REMOVE the
configuration in the server itself that instructed it NOT to cache pages
ending in "php", before php could send the cache headers to the
browser.
In other words, afaik, php headers are supposed to implicitly have
precedence over default server headers, this can further be ensured by
using the optional second parameter/argument to the header function, and
specifying it to be "true". Both ways php's headers that i wrote
procedurally were never sent to the browser. I had to remove my
configuration in the webserver (httpd.conf) that specified that php
pages are not to be cached. Only then did my php headers that i
specified get output to the client.
The if-modified-since header is not being sent by the browser on
subsequent requests, but that has nothing to do with this bug, and that
is a subject that i am still investigating as a separate issue. I just
mentioned it because i'm retarded, and like to ramble....
Thanx ;)
------------------------------------------------------------------------
[2009-11-24 20:18:59] srina...@php.net
can you kindly rephrase your question. i am not too sure i understand
your question here.
If I understand you correctly, you want to find out a way so that
client (like browser) can request this page with 'If-Modified-Since' in
its header so that the server doesn't have to send it again.
if this is your question, then this is a server configuration issue and
nothing to do with a php engine.
------------------------------------------------------------------------
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/50276
--
Edit this bug report at http://bugs.php.net/?id=50276&edit=1
