ID: 48190
Updated by: iliaa@php.net
Reported By: carsten_sttgt at gmx dot de
-Status: Assigned
+Status: Closed
Bug Type: HTTP related
Operating System: *
PHP Version: 5.*, 6
Assigned To: garretts
New Comment:
This bug has been fixed in SVN.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2009-12-29 15:57:54] svn@php.net
Automatic comment from SVN on behalf of iliaa
Revision: http://svn.php.net/viewvc/?view=revision&revision=292762
Log: Fixed bug #48190 (Content-type parameter "boundary" is not
case-insensitive in HTTP uploads).
------------------------------------------------------------------------
[2009-11-30 20:03:46] jani@php.net
So, where's the fix?
------------------------------------------------------------------------
[2009-10-07 22:28:19] garretts@php.net
I'm testing a fix I've built for this right now.
------------------------------------------------------------------------
[2009-05-09 04:08:27] jani@php.net
Yes, I know it's not an upload per se, but the code that handles is one
that most of the time takes care of file uploads. :)
Problem is in rfc1867.c:804, strstr() should be replaced with something
that does the same but case-insensitively.
------------------------------------------------------------------------
[2009-05-08 23:23:57] carsten_sttgt at gmx dot de
> Just curious, but what client actually uses> uppercase/mixed case "boundary" parameter name?
I'm using imap_mail_compose() to build the 'header' and 'content' keys
in the stream_context_create() options array. And then using this
context with e.g. file_get_contents() to make the POST request.
BTW: The above example is a HTTP POST request without a file upload.
------------------------------------------------------------------------
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/48190--
Edit this bug report at http://bugs.php.net/?id=48190&edit=1