Closed svperfecta closed 12 years ago
Any chance someone else could see if they are getting the same thing? It happens to me for JS files too.
I found this bug late last night. It was in PAKE. I found it by doing:
if (headers_sent($filename, $linenum)) { echo "Headers already sent in $filename on line $linenum\n"; }
I'm using the Server module using the example on the PIPE homepage. I'm having a strange problem. No matter what I do I'm getting a content type back of
text/html
. I'm using PHP 5.3.16 (installed via homebrew-php), NGINX, and FPM.First, the file:
And here are the headers:
Here's my NGINX config (pretty vanilla):
If I echo the response object in my assets.php file I get:
I can't see anything wrong anywhere. NGINX isn't touching the headers, PHP-FPM doesn't seem to have any option to manipulate them even if I wanted to, and PHP seems to be sending them correctly. I was wondering if I was missing something obvious?