Your message dated Fri, 13 Jan 2017 13:05:30 +0000
with message-id <e1cs1xu-0009dr...@fasolo.debian.org>
and subject line Bug#841781: Removed package(s) from unstable
has caused the Debian Bug report #795572,
regarding getallheaders for php-fpm patch ignores Content-Type and
Content-Length headers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
795572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php5-fpm
Version: 5.6.9+dfsg-0+deb8u1
Severity: normal
The php5 package in Debian carries a patch to add the getallheaders
function to FastCGI (fpm) build. This function is not supported for this
build upstream at all. See
debian/patches/0046-getallheaders-for-php-fpm-62596.patch
This patch works for "normal" headers which are translated to HTTP_XXX
environment variables by PHP, but it does not work for the Content-Type
and Content-Length headers. There is code in the patch that is supposed
to cover this case, but it does not work. The two headers are missing
from the array returned by getallheaders.
Here is sample code to demonstrate the issue.
# cat getallheaders.php
<?php
var_dump(getallheaders());
var_dump($_SERVER);
?>
$ POST -U -H "X-DUMMY: my test header" -c text/xml
http://myserver/getallheaders.php
Please enter content (text/xml) to be POSTed:
adsflkj öalksjdf ölkjasdf
POST https://ubol.ch/getallheaders.php
User-Agent: lwp-request/6.09 libwww-perl/6.13
Content-Length: 28
Content-Type: text/xml
X-DUMMY: my test header
array(5) {
["Te"]=>
string(18) "deflate,gzip;q=0.3"
["Connection"]=>
string(9) "TE, close"
["Host"]=>
string(7) "myserver"
["User-Agent"]=>
string(33) "lwp-request/6.09 libwww-perl/6.13"
["X-Dummy"]=>
string(14) "my test header"
}
array(37) {
[...]
["FCGI_ROLE"]=>
string(9) "RESPONDER"
["SCRIPT_URL"]=>
string(18) "/getallheaders.php"
["SCRIPT_URI"]=>
string(33) "http://myserver/getallheaders.php";
["HTTP_TE"]=>
string(18) "deflate,gzip;q=0.3"
["HTTP_CONNECTION"]=>
string(9) "TE, close"
["HTTP_HOST"]=>
string(7) "ubol.ch"
["HTTP_USER_AGENT"]=>
string(33) "lwp-request/6.09 libwww-perl/6.13"
["CONTENT_LENGTH"]=>
string(2) "28"
["CONTENT_TYPE"]=>
string(8) "text/xml"
["HTTP_X_DUMMY"]=>
string(14) "my test header"
[...]
}
As you can see, the Content-Type and Content-Length headers are being sent and
also end up in the $_SERVER array, but they are not returned by getallheaders.
To be honest I'm not sure if it's a good idea to carry a patch which
changes upstream behavior like this. While it solves the issue for code
that unconditionally calls getallheaders it breaks code (like in my
case) which checks for getallheaders and only uses the function if it
exists. My code was then broken because the getallheaders implementation
was not the same as when running as an Apache module.
I found and investigated this buug on a jessie system, but the patch in
question is the same in the current unstable version of PHP.
Gaudenz
--- End Message ---
--- Begin Message ---
Version: 5.6.26+dfsg-1+rm
Dear submitter,
as the package php5 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/841781
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
