#19768 [Bgs->Opn]: Expires header incorrectly set, cannot be overwritten

ID: 19768 User updated by: php@savignano.de Reported By: php@savignano.de -Status: Bogus +Status: Open Bug Type: Session related Operating System: Win32, Unix PHP Version: 4.2.1 New Comment: Judging from http://www.w3.org/Protocols/HTTP/1.0/spec.html#Expires the Expires header was the intended header in HTTP/1.0 for cache control. I do not understand why you say, a past header should be sent instead of a correct date. header() doesn't enable me to replace an Expires header, as stated in my original report. Previous Comments: ------------------------------------------------------------------------ [2002-10-28 23:23:03] yohgaki@php.net Since HTTP/1.0 lacks cache control feature can be found in HTTP/1.1, past date expire header should be sent. It's not a bug, but a intended behavior for HTTP/1.0 clients. See also header() manual page to replace header, but add new one. ------------------------------------------------------------------------ [2002-10-26 11:23:15] php@savignano.de Also see my detailed comment on bug #5415 http://bugs.php.net/bug.php?id=5415 ------------------------------------------------------------------------ [2002-10-26 11:08:26] php@savignano.de I did use "private", but this causes incorrect Expires headers as described. That's why I switched to "none" and created the headers myself. ------------------------------------------------------------------------ [2002-10-21 14:55:10] php@savignano.de There seems to be a misunderstanding: Using session_cache_limiter("private") will create the malformed Expires headers mentioned in my bug report. ------------------------------------------------------------------------ [2002-10-20 13:04:06] sas@php.net The default value 'nocache' means that the page should not be cached at all. Have a look at php.ini-dist, you probably want to set session.cache_limiter to 'private'. ------------------------------------------------------------------------ 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/19768 -- Edit this bug report at http://bugs.php.net/?id=19768&edit=1