Edit report at https://bugs.php.net/bug.php?id=60898&edit=1
ID: 60898
Comment by: grzegorz129 at gmail dot com
Reported by: grzegorz129 at gmail dot com
Summary: Failed to upload files when content-type contain
charset
Status: Open
Type: Bug
Package: *General Issues
Operating System: Linux
PHP Version: 5.3.9
Block user comment: N
Private report: N
New Comment:
Unfortunately I have no access to application frontend code, but I know it's
network side was wrote using CFNetwork framework -
https://developer.apple.com/library/mac/#documentation/Networking/Conceptual/CFNe
twork/Introduction/Introduction.html
Charset in "Content-type" is used in eg. RFC2045 [2nd page], so I think it's
valid :)
Previous Comments:
------------------------------------------------------------------------
[2012-05-18 03:10:13] reeze dot xia at gmail dot com
Hi,
how do you build the post header? by your own or with curl or such tools?
The multipart itself didn't have any charset, every part could set its charset,
but the whole part.
Thanks.
------------------------------------------------------------------------
[2012-03-05 11:25:20] grzegorz129 at gmail dot com
Any news on this annoying bug?
------------------------------------------------------------------------
[2012-01-27 03:36:24] grzegorz129 at gmail dot com
Description:
------------
When I try to upload files using HTTP post with header "Content-Type:
multipart/form-data; boundary=-----NPRequestBoundary-----" everything works as
expected but trying to use "Content-Type: multipart/form-data; boundary=-----
NPRequestBoundary-----; charset=UTF-8" cause completely blank $_FILES array.
Expected result:
----------------
Full $_FILES array
Actual result:
--------------
Empty $_FILES array
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=60898&edit=1
