Bug #60928 [Opn->Fbk]: php crash after http post without content type header set
| From: | cataphract@php.net | Date: | Thu, 02 Feb 2012 08:47:30 +0000 |
| Subject: | Bug #60928 [Opn->Fbk]: php crash after http post without content type header set | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-167055@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=60928&edit=1
ID: 60928
Updated by: cataphract@php.net
Reported by: bardobakker at gmail dot com
Summary: php crash after http post without content type
header set
-Status: Open
+Status: Feedback
Type: Bug
Package: Apache2 related
Operating System: Linux
PHP Version: 5.3.9
Block user comment: N
Private report: N
Previous Comments:
------------------------------------------------------------------------
[2012-02-02 08:46:57] cataphract@php.net
You can disable mbstring by commenting out the "extension=mbstring.so" line from the
configuration file and restarting Apache (and then confirm "mbstring" doesn't show up
in phpinfo()).
------------------------------------------------------------------------
[2012-01-31 22:31:09] bardobakker at gmail dot com
php.ini has the default mbstring options = everything commented out
mbstring.ini has only the line:
extension=mbstring.so
In a local .htaccess file I added:
php_value mbstring.http_input pass
php_value mbstring.http_output pass
php_value mbstring.encoding_translation 0
which doesn't change anything in the output of phpinfo()
How would you disable mbstring?
Can it have something to do with mime type stuff or so?
Output phpinfo: http://www.mymoza.com/tup/info.php
------------------------------------------------------------------------
[2012-01-31 21:54:31] cataphract@php.net
I can't reproduce the error. Could you try disabling mbstring? And if, after
disabling mbstring, there's no segfault, please tell us your configuration for
mbstring.* ini options (those active for the script that receives the POST
request).
------------------------------------------------------------------------
[2012-01-31 21:04:01] bardobakker at gmail dot com
Hi,
First of all, a surprising header in tcp dump (for me), I thought content type was not set, but:
POST /tup/up.php HTTP/1.1
Content-Length: 1038349
Connection: Keep-Alive
Accept-Encoding: gzip
Accept-Language: nl-NL,en,*
User-Agent: Mozilla/5.0
Host: www.mymoza.com
Content-Type: application/x-www-form-urlencoded
URL of tcpdump (libpcap format): http://www.mymoza.com/tup/tcpdump.data
URL of test image: http://www.mymoza.com/tup/image.jpg
With the following headers set no seg. fault will occur:
POST /tup/up.php HTTP/1.1
Content-Type: image/jpeg
Content-Length: 1038349
Connection: Keep-Alive
Accept-Encoding: gzip
Accept-Language: nl-NL,en,*
User-Agent: Mozilla/5.0
Host: www.mymoza.com
------------------------------------------------------------------------
[2012-01-31 06:36:10] pajoye@php.net
Can you post a link to the data you use to upload?
Please try to do a tcpdump as well on the client side to see what you send
actually and post a link to the dump here as well.
We still cannot reproduce it, even with large data.
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=60928
--
Edit this bug report at https://bugs.php.net/bug.php?id=60928&edit=1