|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2015-07-16 08:09 UTC] mike@php.net
-Status: Open
+Status: Not a bug
[2015-07-16 08:09 UTC] mike@php.net
[2015-07-16 11:18 UTC] mike@php.net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Tue Oct 28 14:00:01 2025 UTC |
Description: ------------ When HTTP status 304 is set, Apache appears to ignore any other headers. X- Powered-By is also missing, which was the first hint that something was up in either the SAPI or Apache. I'm not fully sure this is a PHP bug, or an Apache bug though, so feel free to close it if I put it in the wrong space. The practical use-case I have for this is the so-called CORS headers. When I do a cross-domain request within firefox, and CORS headers have expired firefox requires them to be set, even for the 304 response. Since they get stripped, firefox just throws an error. Test script: --------------- header('HTTP/1.1 304 Not Modified') header('X-Foo: Bar'); Expected result: ---------------- The X-Foo header returned Actual result: -------------- All custom headers are ignored