[GH-ISSUE #113] Request Body Is Not Sent #48

New issue

Closed

opened 2026-03-16 12:58:22 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 12:58:22 +03:00

Owner

Originally created by @amxmln on GitHub (Aug 30, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/113

Originally assigned to: @NBTX on GitHub.

Describe the bug
During a POST/CREATE/PUT/PATCH request the request body is not actually being sent.

To Reproduce
Steps to reproduce the behavior:

Go to postwoman.io
Switch to POST
Enter: https://jsonplaceholder.typicode.com as URL and /users as path
Add a field "name" with value "foo"
Send the request
Check the response and see missing field "name" with value "foo"

Expected behavior
The response should be { "name":"foo", "id": 11}

Desktop (please complete the following information):

OS: Ubuntu 18.04
Browser: Chrome (Incognito Tab)
Version: 76

Additional context
I’ve tested this both with a local development project as well as the JSONPlaceholder API and the results are both the same. This problem did not yet occur 20 hours ago, so perhaps it’s a regression from one of the more recent commits.

Originally created by @amxmln on GitHub (Aug 30, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/113 Originally assigned to: @NBTX on GitHub. **Describe the bug** During a POST/CREATE/PUT/PATCH request the request body is not actually being sent. **To Reproduce** Steps to reproduce the behavior: 1. Go to postwoman.io 2. Switch to POST 3. Enter: `https://jsonplaceholder.typicode.com` as URL and `/users` as path 4. Add a field "name" with value "foo" 5. Send the request 6. Check the response and see missing field "name" with value "foo" **Expected behavior** The response should be `{ "name":"foo", "id": 11}` **Desktop (please complete the following information):** - OS: Ubuntu 18.04 - Browser: Chrome (Incognito Tab) - Version: 76 **Additional context** I’ve tested this both with a local development project as well as the JSONPlaceholder API and the results are both the same. This problem did not yet occur 20 hours ago, so perhaps it’s a regression from one of the more recent commits.

kerem

2026-03-16 12:58:22 +03:00

closed this issue
added the
bug

critical
labels

kerem commented

2026-03-16 12:58:38 +03:00

Author

Owner

@NBTX commented on GitHub (Aug 30, 2019):

Looking into it now. I suspect this is after the axios migration.

@NBTX commented on GitHub (Aug 30, 2019): Looking into it now. I suspect this is after the axios migration.

kerem commented

2026-03-16 12:58:43 +03:00

Author

Owner

@amxmln commented on GitHub (Aug 30, 2019):

I can confirm it is working again on my end as well! 👍 Thanks for the quick response & fix.

@amxmln commented on GitHub (Aug 30, 2019): I can confirm it is working again on my end as well! :+1: Thanks for the quick response & fix.

kerem referenced this issue

2026-03-17 00:05:31 +03:00

[PR #48] [MERGED] 🔌 Add websocket support #2382

kerem referenced this issue

2026-03-17 00:05:47 +03:00

[PR #51] [MERGED] Migrate nuxt #2389