[GH-ISSUE #265] POSTing large raw JSON packets #89

New issue

Closed

opened 2026-03-16 13:20:30 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 13:20:30 +03:00

Owner

Originally created by @AtomicMaya on GitHub (Nov 4, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/265

Describe the bug
Given huge packets, PW throws a URI too long HTTP error, and won't finish the request.

To Reproduce
Steps to reproduce the behavior:

Have an endpoint that can receive a request (node + JS, other).
On PW send POST with RAW input, with excess of 4000 characters or so.
Send.

Expected behavior
Should POST without error.

Suggested fixes

Send content as raw bytes in request body, as per the Volley API and others.

Desktop (please complete the following information):

OS: Win10
Browser Opera | Chrome | Firefox | Edge
Version latest

Additional context
Trying to test my own API with heavy loads, PW can't handle it for the moment, sadly.

Originally created by @AtomicMaya on GitHub (Nov 4, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/265 **Describe the bug** Given huge packets, PW throws a URI too long HTTP error, and won't finish the request. **To Reproduce** Steps to reproduce the behavior: 1. Have an endpoint that can receive a request (node + JS, other). 2. On PW send POST with RAW input, with excess of 4000 characters or so. 3. Send. **Expected behavior** Should POST without error. **Suggested fixes** - Send content as raw bytes in request body, as per the Volley API and others. **Desktop (please complete the following information):** - OS: Win10 - Browser Opera | Chrome | Firefox | Edge - Version *latest* **Additional context** Trying to test my own API with heavy loads, PW can't handle it for the moment, sadly.

kerem

2026-03-16 13:20:30 +03:00

closed this issue
added the
bug

help wanted
labels

kerem commented

2026-03-16 13:20:47 +03:00

Author

Owner

@GiantRobato commented on GitHub (Nov 28, 2019):

Just tried a POST to an endpoint with 6000+ and 12K+ chars and couldn't reproduce. Are you still having this issue?

@GiantRobato commented on GitHub (Nov 28, 2019): Just tried a POST to an endpoint with 6000+ and 12K+ chars and couldn't reproduce. Are you still having this issue?

kerem commented

2026-03-16 13:20:52 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 28, 2019):

@AtomicNicos have you tried reproducing the issue after #292 ? If issue is fixed, feel free to this.

@liyasthomas commented on GitHub (Nov 28, 2019): @AtomicNicos have you tried reproducing the issue after #292 ? If issue is fixed, feel free to this.

kerem commented

2026-03-16 13:20:57 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 1, 2019):

https://stackoverflow.com/questions/55631057/axios-post-data-as-form-data-instead-of-as-json-in-payload

@liyasthomas commented on GitHub (Dec 1, 2019): https://stackoverflow.com/questions/55631057/axios-post-data-as-form-data-instead-of-as-json-in-payload

kerem commented

2026-03-16 13:21:02 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 14, 2019):

From https://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error it is clearly evident that this error is a limitation from the server side and got nothing to do with PW - hence closing the issue.

@liyasthomas commented on GitHub (Dec 14, 2019): From https://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error it is clearly evident that this error is a limitation from the server side and got nothing to do with PW - hence closing the issue.

kerem referenced this issue

2026-03-17 00:06:55 +03:00

[PR #89] [MERGED] Websocket log auto scroll to bottom #2410