-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why misorder of operations and map will cause error thrown? #372
Comments
Multipart HTTP requests definitely support ordering fields in the request; they are streamed one after another in the request body. If certain clients don't allow you to specify the order of fields, then I would consider that an issue with the client that needs to be improved. Even if we relax this |
In this scenario, seems like file is always composing in the last position. (idk why). And I do some research and w3c form spec said
So it looks like golang's stdlib didn't implement formdata correctly, try to find some other solution. |
Closing because |
I'm not quitely sure if formdata has order, but some http client implementation, like go http client, use map[string][]string as formdata's data structure which has no order, may cause the order is unreliable on client side.
I read source code and found parsing
map
requireoperations
, but if make a change like this(a tempo workaround, test not updated and may need update), it can whateveroperations
come first ormap
come first.4a79f7d
ff we get
map
first, just delay resolve after we getoperations
, if we getoperations
first, work like normal.The text was updated successfully, but these errors were encountered: