Edit report at http://bugs.php.net/bug.php?id=46703&edit=1
ID: 46703 User updated by: zent at piments dot com Reported by: zent at piments dot com Summary: default headers blocks correct http responce Status: Bogus Type: Feature/Change Request Package: *General Issues Operating System: linux PHP Version: 5.2.6 Block user comment: N Private report: N New Comment: I find it hard to understand how you can maintain that unconditionally adding incorrect headers to legitimate output is not a bug. If the spec required headers there *may* be some case to argue for adding a default, but that is not the case. Please reopen or fix this bug. Previous Comments: ------------------------------------------------------------------------ [2011-04-09 07:52:33] zent at piments dot com using an extra step : using header() as you suggest is a workaround and does not make the bug "bogus". As I said in the bug report, not sending a header is legit according to the spec and would produce correct results but for this BUG inserting *incorrect* headers without being asked. Sorry that's a bug. Your suggested solution is a workaround for that bug. ------------------------------------------------------------------------ [2011-04-08 20:50:58] j...@php.net Just set the correct header with header(). No bug here. ------------------------------------------------------------------------ [2008-11-27 23:47:52] zent at piments dot com Description: ------------ if no call is made to header() , php inserts Content-Type: text/html this may well be incorrect, as for example in creating image/png HTTP spec allows sending content without a content-type header and allows the client to detect type from the data, in this case first four bytes are %PNG However, this content sniffing is allowed "if and only if" there are no headers explicitly present. Thus in adding a default text (or other inappropriate default) header php is preventing the client from correctly displaying the data. Reproduce code: --------------- <?php $i=imagecreate(....); imagepng($i); imagedestroy($i); ?> Expected result: ---------------- data served without content-type header and correctly interpreted by client sniffing content as defined in spec. Actual result: -------------- incorrect insertion of erroneous header forces image data to be displayed as text. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=46703&edit=1
