Anyone can comment on a bug. Have a simpler test case? Does it
work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please
!

Your email address:MUST BE VALID

Solve the problem:25 - 24 = ?

Subscribe to this entry?

[2014-01-07 16:50 UTC] julian at julianrhindconsulting dot com

Description:
------------
Hi
There appears to be a problem with the current curl implementation in regard to duplicate post fields - especially when also wanting to post files
In order to call curl_setopt option CURLOPT_POSTFIELDS with the following data
name=Bob
name=Mary
this can be done using the string form passing
'name=Bob&name=Mary'
however it can't be done using the array form
['name'=>'Bob', 'name'=>'Mary']
for obvious reasons
When posting files it appears to be a requirement to use the array form
So what is one to do - if one wants to post duplicate field names and files?
This bug/design problem appears to be long standing and is inquired widely on the internet - however no one appears to be trying to resolve it
Is it possible this could be resolved?
The simplest solution would appear to be to handle a field name pointing to an array as a duplicate field name - so one would specify
[name=>['Bob','Mary']]
and curl_setopt would generate
name=Bob&name=Mary
I also note that this exact problem occurs when receiving posted data via $_POST - again the same solution could be used - duplicate posted fields would return an array rather than a single value
I'm also aware of a workaround - using
['name[0]'=>'Bob','name[1]'=>'Mary']
however this does not generate the correct post data - but may be understood by the server if it happens to be running PHP
Regards
Julian
Julian Rhind
Expected result:
----------------
name=Bob&name=Mary
Actual result:
--------------
name=Mary

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2014-01-08 23:41 UTC] cmbecker69 at gmx dot de

duplicate of #51634

[2014-01-09 05:58 UTC] julian at julianrhindconsulting dot com

Hi Christoph
Thanks - I see it has been reported - nearly four years ago - the problem is that a patch has been added to that bug claiming to fix the problem - however the problem remains - presumably that's why the bug has not been fixed - it's got trapped in the system - apparently fixed - but not - is it possible that the bug could get fixed?
Regards
Julian