[GH-ISSUE #4854] [bug]: Post params / Content-type is not not being set after upgrading #1825

Closed
opened 2026-03-16 21:55:42 +03:00 by kerem · 5 comments
Owner

Originally created by @jkthoppil on GitHub (Mar 6, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4854

Originally assigned to: @CuriousCorrelation on GitHub.

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

Even though we've set the post params (Tried setting Content-Type to multipart/form-data and application/json) But I'm not receiving it in the server.

My Request:
curl --request POST \ --url 'https://echo.qubit.codes/?qp=1' \ --header 'content-type: multipart/form-data' \ --form fd=1

Response:
{ "method": "POST", "url": "https://echo.qubit.codes/", "full_url": "https://echo.qubit.codes/?qp=1", "path": "/", "segments": [], "query_params": { "qp": "1" }, "post_params": [], "all_params": { "qp": "1" }, "files": [], "headers": { "Content-Type": "multipart/form-data", "Accept-Encoding": "deflate, gzip", "Accept": "*/*", "Content-Length": "0", "Connection": "close", "X-Forwarded-For": "49.37.233.114", "Host": "echo.qubit.codes" }, "cookies": [], "ip": "49.37.233.114", "time": "2025-03-06T15:21:12+00:00", "is_secure": true, "ajax": false, "is_json": false, "decoded_content": "" }

Steps to reproduce

  1. Add the URL
  2. Set the Content Type
  3. Add Request Body
  4. Submit the request

Environment

Production

Version

Cloud

Originally created by @jkthoppil on GitHub (Mar 6, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4854 Originally assigned to: @CuriousCorrelation on GitHub. ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current behavior Even though we've set the post params (Tried setting Content-Type to multipart/form-data and application/json) But I'm not receiving it in the server. My Request: ` curl --request POST \ --url 'https://echo.qubit.codes/?qp=1' \ --header 'content-type: multipart/form-data' \ --form fd=1 ` Response: ` { "method": "POST", "url": "https://echo.qubit.codes/", "full_url": "https://echo.qubit.codes/?qp=1", "path": "/", "segments": [], "query_params": { "qp": "1" }, "post_params": [], "all_params": { "qp": "1" }, "files": [], "headers": { "Content-Type": "multipart/form-data", "Accept-Encoding": "deflate, gzip", "Accept": "*/*", "Content-Length": "0", "Connection": "close", "X-Forwarded-For": "49.37.233.114", "Host": "echo.qubit.codes" }, "cookies": [], "ip": "49.37.233.114", "time": "2025-03-06T15:21:12+00:00", "is_secure": true, "ajax": false, "is_json": false, "decoded_content": "" } ` ### Steps to reproduce 1. Add the URL 2. Set the Content Type 3. Add Request Body 4. Submit the request ### Environment Production ### Version Cloud
kerem 2026-03-16 21:55:42 +03:00
Author
Owner

@bobbysciacchitano commented on GitHub (Mar 7, 2025):

Can confirm this is the case for setting the body type to application/json for a POST request.

<!-- gh-comment-id:2705547432 --> @bobbysciacchitano commented on GitHub (Mar 7, 2025): Can confirm this is the case for setting the body type to application/json for a POST request.
Author
Owner

@ddbdzung commented on GitHub (Mar 7, 2025):

Can confirm this is the case for setting the body type to application/json for a POST request.

Yes, I confirm that this happens when setting the content type to application/json for a POST request.

<!-- gh-comment-id:2705681709 --> @ddbdzung commented on GitHub (Mar 7, 2025): > Can confirm this is the case for setting the body type to application/json for a POST request. Yes, I confirm that this happens when setting the content type to application/json for a POST request.
Author
Owner

@gladykov commented on GitHub (Mar 7, 2025):

Can confirm with multipart/form-data

All I recieve is file attachment, but not text values

<!-- gh-comment-id:2706185015 --> @gladykov commented on GitHub (Mar 7, 2025): Can confirm with `multipart/form-data` All I recieve is file attachment, but not text values
Author
Owner

@jamesgeorge007 commented on GitHub (Mar 11, 2025):

Hi, we have a PR with the fix scheduled for the next patch release.

<!-- gh-comment-id:2713644428 --> @jamesgeorge007 commented on GitHub (Mar 11, 2025): Hi, we have a [PR](https://github.com/hoppscotch/hoppscotch/pull/4860) with the fix scheduled for the next patch release.
Author
Owner

@jamesgeorge007 commented on GitHub (Mar 13, 2025):

Closing this issue since it's resolved in the latest release. Please let us know if you have any feedback.

<!-- gh-comment-id:2720067961 --> @jamesgeorge007 commented on GitHub (Mar 13, 2025): Closing this issue since it's resolved in the latest release. Please let us know if you have any feedback.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#1825
No description provided.