Edit report at http://bugs.php.net/bug.php?id=52674&edit=1
ID: 52674
Updated by: f...@php.net
Reported by: php-bugs at majkl578 dot cz
Summary: [FPM] Status page returns inconsistent Content-Type
headers
Status: Closed
Type: Bug
Package: FPM related
Operating System: Linux Debian
PHP Version: 5.3.3
Assigned To: fat
Block user comment: N
Private report: N
New Comment:
this is an upgrade option only
Previous Comments:
------------------------------------------------------------------------
[2011-01-18 20:26:41] 1 dot david dot michael at gmail dot com
Is there a work around with apache to avoid upgrading to 5.3.4 or 5.3.5?
Or is
upgrading the only option?
------------------------------------------------------------------------
[2010-08-23 22:41:56] f...@php.net
This bug has been fixed in SVN.
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/.
Thank you for the report, and for helping us make PHP better.
------------------------------------------------------------------------
[2010-08-23 22:40:46] f...@php.net
Automatic comment from SVN on behalf of fat
Revision: http://svn.php.net/viewvc/?view=revision&revision=302721
Log: - Fixed bug #52674 (FPM Status page returns inconsistent
Content-Type headers).
------------------------------------------------------------------------
[2010-08-23 10:38:51] f...@php.net
Moreover, the Content-Type used for json was not the best choice. It was
application/jsonrequest.
As specified in RFC4627, it should be application/json.
------------------------------------------------------------------------
[2010-08-23 10:28:43] f...@php.net
The status page does not return a valid Content-Type header:
...
text/plain
Content-type: text/plain
...
it should be
...
Content-type: text/plain
...
It affects apache but also any other front web servers. Nginx is more
tolerant
and ignores unknown / malformed headers but text/html was use instead.
------------------------------------------------------------------------
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/bug.php?id=52674
--
Edit this bug report at http://bugs.php.net/bug.php?id=52674&edit=1
