#41349 [Opn->Bgs]: $_POST not filled, altough raw POST is available

ID: 41349 Updated by: tony2001@php.net Reported By: php at bitrockers dot de -Status: Open +Status: Bogus Bug Type: HTTP related Operating System: Linux Debian Etch PHP Version: 5.2.2 New Comment: >Ok, so what's the difference for Apache? I can see it maintains a registry of methods in upper case. >Maybe that would save a lot of developers Even if it's really can be worked around in PHP, you still would not be able to use it since it takes a lot of time for a new version to get installed on all servers on this planet. Previous Comments: ------------------------------------------------------------------------ [2007-05-10 21:58:08] php at bitrockers dot de Ok, so what's the difference for Apache? However... today I discovered that our javascript library calls the XmlHttpRequest with lowercase 'post', and because some weird reasons some IE6 installations doesn't translate that into uppercase 'POST'. So maybe it's not PHP to blame for this, but unfortunately there are a couple of javascript libraries which indeed use 'post' instead of POST (e.g. mootools, prototype). There even were a post on the Webkit-mailinglist about that: http://lists.macosforge.org/pipermail/webkit-unassigned/2006-March/006858.html Therefore, if it's not too much work it would be a good idea to also populate the $_POST variable when the request is 'post'. Maybe that would save a lot of developers which rely on so popular javascript-frameworks like prototype or mootools a lot of headaches. In the end, of course, it's microsoft bug ( IE6 should have translated post to POST or at least throw an error about that). ------------------------------------------------------------------------ [2007-05-10 20:23:00] tony2001@php.net From what I can see, it makes difference for Apache. ------------------------------------------------------------------------ [2007-05-10 16:44:50] php at bitrockers dot de Could it be a problem that the POST request comes as "post". Here an excerpt of our logfile: Customers (not working) request: "post /ajax/mypageProfileEdit/? HTTP/1.1" 200 99 "application/x-www-form-urlencoded; charset=utf-8" "148" Request (my IE6, working): "POST /ajax/mypageProfileEdit/? HTTP/1.1" 200 123 "application/x-www-form-urlencoded; charset=utf-8" "148" Does it make a difference for PHP if the POST request is lowercase? Apache doesn't seem to have a problem with that. I don't know why the customers IE6 sends XmlHttpRequest as lowercase "post"? ------------------------------------------------------------------------ [2007-05-10 15:28:45] php at bitrockers dot de (damn, destroyed the Summary) :) ------------------------------------------------------------------------ [2007-05-10 15:27:13] php at bitrockers dot de I've actually activated the logging of Content-Type and Content-Length. Now I have to ask the customers, which are having the problems, to try again. As soon as I get the response, I will post the Content-Type of their requests. ------------------------------------------------------------------------ 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/41349 -- Edit this bug report at http://bugs.php.net/?id=41349&edit=1