#39989 [Com]: header location doesn't send explanation

ID: 39989 Comment by: l dot bigonville at edpnet dot be Reported By: Laurent Bigonville <l dot bigonville at edpnet dot Status: Feedback Bug Type: HTTP related Operating System: Debian Sarge PHP Version: 5.2.0 New Comment: I use php in cgi mode. The problem seems to come from apache 2.0(.54) not from php. I'v made an other test using a simple shell script #! /bin/sh echo Status: 302 echo With apache 2.2 it returns HTTP/1.1 302 Found but with apache 2.0 it returns HTTP/1.1 302 If I change the script to #! /bin/sh echo Status: 302 echo It returns HTTP/1.1 302 Found i both cases Previous Comments: ------------------------------------------------------------------------ [2006-12-30 02:03:28] iliaa@php.net What SAPI are you using? ------------------------------------------------------------------------ [2006-12-30 01:06:35] l dot bigonville at edpnet dot be I think it's because php_cgi return "Status: 302" with no explanation ------------------------------------------------------------------------ [2006-12-30 00:33:09] l dot bigonville at edpnet dot be This is odd the problem occurs with the dotdeb packages on sarge but not with debian's official packages on etch.. ------------------------------------------------------------------------ [2006-12-30 00:24:39] Laurent Bigonville <l dot bigonville at edpnet dot Description: ------------ the header location doesn't conform to RFC. The response header must finish with at least a space character. Reproduce code: --------------- header("Location: http://url/); Expected result: ---------------- According to RFC2616 §6.1 the response message must consist in "HTTP-Version SP Status-Code SP Reason-Phrase CRLF". (ie HTTP/1.1 302 Found). Actual result: -------------- Currently, php send "HTTP/1.1 302" with even no space at the end of the response ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=39989&edit=1