starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #1833] The fields of a request with body type multipart/form-data do not follow the order configured in the request #582

New issue

Closed

opened 2026-03-16 16:07:28 +03:00 by kerem · 13 comments

kerem commented

2026-03-16 16:07:28 +03:00

Owner

Originally created by @sawa-ko on GitHub (Sep 20, 2021).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1833

Describe the bug
I have noticed that when sending a request, the order of the fields set in the request body configuration is not followed, and this can cause failures in applications where a specific order must be followed in the body fields.

I noticed that because with hoppscotch when I try to send this request to my graphql server with graphql-upload, I get this error, and that error is because the file fields are not followed by the map field, so the error appears.

And I don't think it is graphql-upload error because I make exactly the same request with postman and it works correctly.

To Reproduce
Steps to reproduce the behavior:

Go to 'rest section'
Create a request with body of type multipart/form-data
Click on 'Send'
See error

Expected behavior
That the body fields have the same order as configured in the request when sending the request to the server.

Screenshots

https://user-images.githubusercontent.com/56084970/133948340-8b6f9fb4-d80b-4d5c-b049-8d582d51126c.mp4

Desktop (please complete the following information):

OS: Windows
Browser: edge
Version 93.0.961.52

Additional context
I don't know if the same is true for other types of request body.

Originally created by @sawa-ko on GitHub (Sep 20, 2021). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/1833 **Describe the bug** I have noticed that when sending a request, the order of the fields set in the request body configuration is not followed, and this can cause failures in applications where a specific order must be followed in the body fields. I noticed that because with hoppscotch when I try to send this request to my graphql server with graphql-upload, I get this error, and that error is because the file fields are not followed by the map field, so the error appears. And I don't think it is graphql-upload error because I make exactly the same request with postman and it works correctly. **To Reproduce** Steps to reproduce the behavior: 1. Go to 'rest section' 2. Create a request with body of type multipart/form-data 3. Click on 'Send' 4. See error **Expected behavior** That the body fields have the same order as configured in the request when sending the request to the server. **Screenshots** https://user-images.githubusercontent.com/56084970/133948340-8b6f9fb4-d80b-4d5c-b049-8d582d51126c.mp4 **Desktop (please complete the following information):** - OS: Windows - Browser: edge - Version 93.0.961.52 **Additional context** I don't know if the same is true for other types of request body.

kerem

2026-03-16 16:07:28 +03:00

closed this issue
added the
bug

good first issue
labels

kerem commented

2026-03-16 16:07:44 +03:00

Author

Owner

@liyasthomas commented on GitHub (Sep 20, 2021):

Thanks for reporting this issue. We're working on a fix. Will update here once it lands on production.

@liyasthomas commented on GitHub (Sep 20, 2021): Thanks for reporting this issue. We're working on a fix. Will update here once it lands on production.

kerem commented

2026-03-16 16:07:49 +03:00

Author

Owner

@mandaputtra commented on GitHub (Oct 1, 2021):

Hi, @kaname-png could you recall the wrong order? I test the step and I got same order as the request. Or maybe I was wrong on testing it?

@mandaputtra commented on GitHub (Oct 1, 2021): Hi, @kaname-png could you recall the wrong order? I test the step and I got same order as the request. Or maybe I was wrong on testing it? ![Screenshot from 2021-10-01 09-09-48](https://user-images.githubusercontent.com/23342943/135554918-02ac745f-b4af-4063-ac36-941319647fb5.png)

kerem commented

2026-03-16 16:07:55 +03:00

Author

Owner

@sawa-ko commented on GitHub (Oct 1, 2021):

As you can see I execute the same request in both applications and I get that error in hoppscotch and in postman I don't get the error I mention.

For what it's worth, I'm using nestjs with graphql and the graphql-upload plugin.

@sawa-ko commented on GitHub (Oct 1, 2021): As you can see I execute the same request in both applications and I get that error in hoppscotch and in postman I don't get the error I mention. For what it's worth, I'm using nestjs with graphql and the graphql-upload plugin.

kerem commented

2026-03-16 16:08:00 +03:00

Author

Owner

@mandaputtra commented on GitHub (Oct 1, 2021):

If you could make some simple repo nestjs + graphql + graphql-upload demonstrating this error. I could work on this issue. I'm just not fond with graphql.

@mandaputtra commented on GitHub (Oct 1, 2021): If you could make some simple repo nestjs + graphql + graphql-upload demonstrating this error. I could work on this issue. I'm just not fond with graphql.

kerem commented

2026-03-16 16:08:05 +03:00

Author

Owner

@rishabhkalra96 commented on GitHub (Oct 9, 2021):

@mandaputtra do we have any update on this ? is it worth looking ?

@rishabhkalra96 commented on GitHub (Oct 9, 2021): @mandaputtra do we have any update on this ? is it worth looking ?

kerem commented

2026-03-16 16:08:10 +03:00

Author

Owner

@mandaputtra commented on GitHub (Oct 9, 2021):

ifyou can reproduce go ahead i never work with graphql

@mandaputtra commented on GitHub (Oct 9, 2021): ifyou can reproduce go ahead i never work with graphql

kerem commented

2026-03-16 16:08:15 +03:00

Author

Owner

@rishabhkalra96 commented on GitHub (Oct 9, 2021):

sure, will try to see if i can reproduce it. Never worked on graphql myself. Is there a way we can have access to any existing graphql api which could produce same issue ? Maybe @kaname-png can help with this ?

@rishabhkalra96 commented on GitHub (Oct 9, 2021): sure, will try to see if i can reproduce it. Never worked on graphql myself. Is there a way we can have access to any existing graphql api which could produce same issue ? Maybe @kaname-png can help with this ?

kerem commented

2026-03-16 16:08:20 +03:00

Author

Owner

@kyteinsky commented on GitHub (Jan 16, 2022):

It is an issue similar to this one, that was posted for postman originally. So essentially 0 is alphabetically ordered and placed before map in the request, which causes the issue here.

It can be a simple fix to work on, just ensuring all file fields come after the map parameter.

Do I have your green flag @liyasthomas to work on this?

@kyteinsky commented on GitHub (Jan 16, 2022): It is an issue similar to [this one](https://stackoverflow.com/questions/49771811/postman-ordering-of-fields-in-form-data-request/53756457), that was posted for postman originally. So essentially `0` is alphabetically ordered and placed before `map` in the request, which causes the issue here. It can be a simple fix to work on, just ensuring all file fields come after the `map parameter`. Do I have your green flag @liyasthomas to work on this?

kerem commented

2026-03-16 16:08:25 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jan 16, 2022):

Hi @kyteinsky, you can give this a try. Do let us know if you've any doubts on the source code.

@liyasthomas commented on GitHub (Jan 16, 2022): Hi @kyteinsky, you can give this a try. Do let us know if you've any doubts on the source code.

kerem commented

2026-03-16 16:08:30 +03:00

Author

Owner

@kyteinsky commented on GitHub (Jan 16, 2022):

Sure thing. Thanks!

@kyteinsky commented on GitHub (Jan 16, 2022): Sure thing. Thanks!

kerem commented

2026-03-16 16:08:35 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jan 21, 2022):

@kaname-png does the implementation in the PR #2067 fix the issues for you ?

You can test the implementation using this Deploy Preview URL: https://deploy-preview-2067--hoppscotch.netlify.app/

@AndrewBastin commented on GitHub (Jan 21, 2022): @kaname-png does the implementation in the PR #2067 fix the issues for you ? You can test the implementation using this Deploy Preview URL: https://deploy-preview-2067--hoppscotch.netlify.app/

kerem commented

2026-03-16 16:08:40 +03:00

Author

Owner

@sawa-ko commented on GitHub (Jan 22, 2022):

@AndrewBastin I can confirm that the problem has indeed been solved.
And sorry for not giving a playground, I didn't see the notification until now.

@sawa-ko commented on GitHub (Jan 22, 2022): @AndrewBastin I can confirm that the problem has indeed been solved. And sorry for not giving a playground, I didn't see the notification until now.

kerem commented

2026-03-16 16:08:45 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Jan 22, 2022):

@kaname-png No worries! Thank you for confirming the fix and your continued contribution to the project! ♥️

@AndrewBastin commented on GitHub (Jan 22, 2022): @kaname-png No worries! Thank you for confirming the fix and your continued contribution to the project! ♥️

kerem referenced this issue

2026-03-17 00:24:08 +03:00

[PR #582] [MERGED] Update link to extension repo in README #2723

kerem referenced this issue

2026-03-17 00:24:08 +03:00

[PR #586] [MERGED] Even #2724