Edit report at https://bugs.php.net/bug.php?id=60898&edit=1

 ID:                 60898
 User updated 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
+Status:             Closed
 Type:               Bug
 Package:            *General Issues
 Operating System:   Linux
 PHP Version:        5.3.9
 Block user comment: N
 Private report:     N

 New Comment:

Fixed in rev #316373 according to bug #55504


Previous Comments:
------------------------------------------------------------------------
[2013-03-08 22:05:46] grzegorz129 at gmail dot com

It seems to be fixed. On 5.5 alpha 6 works as expected.
Is any way to check when it has been repaired?

------------------------------------------------------------------------
[2012-05-22 21:46:03] grzegorz129 at gmail dot com

I've found possible workaround - run script as CGI and parse php://stdin by 
hand 
:)

------------------------------------------------------------------------
[2012-05-18 08:45:47] grzegorz129 at gmail dot com

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 :)

------------------------------------------------------------------------
[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?

------------------------------------------------------------------------


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=60898


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60898&edit=1

Reply via email to