[GH-ISSUE #394] Raw input disabled is not working properly #145

New issue

Closed

opened 2026-03-16 13:40:52 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @elangosundar on GitHub (Dec 3, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/394

Originally assigned to: @liyasthomas on GitHub.

Describe the bug
Raw input disabled is not working properly

To Reproduce
Steps to reproduce the behavior:

To make the api request by using POST methods via RAW INPUT.
Checking the POST api results, it should works as expected.
Now disable the RAW INPUT and will make the GET Request.
Still RAW INPUTS are passing in GET methods and even if RAW INPUTS disabled also.
Please fix this issue.

Expected behavior
If RAW INPUTS is disabled, it should not pass in API request

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [Ubuntu16.04]
Browser [Chrome]
Version []

Originally created by @elangosundar on GitHub (Dec 3, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/394 Originally assigned to: @liyasthomas on GitHub. **Describe the bug** Raw input disabled is not working properly **To Reproduce** Steps to reproduce the behavior: 1. To make the api request by using POST methods via RAW INPUT. 2. Checking the POST api results, it should works as expected. 3. Now disable the RAW INPUT and will make the GET Request. 4. Still RAW INPUTS are passing in GET methods and even if RAW INPUTS disabled also. Please fix this issue. **Expected behavior** If RAW INPUTS is disabled, it should not pass in API request **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - OS: [Ubuntu16.04] - Browser [Chrome] - Version []

kerem

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

closed this issue
added the
need information
label

kerem commented

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

Author

Owner

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

Still RAW INPUTS are passing in GET methods and even if RAW INPUTS disabled also.
Please fix this issue.

I couldn't reproduce this issue. GET doesn't pass raw payload in request.

@liyasthomas commented on GitHub (Dec 3, 2019): > Still RAW INPUTS are passing in GET methods and even if RAW INPUTS disabled also. Please fix this issue. I couldn't reproduce this issue. GET doesn't pass raw payload in request.

kerem commented

2026-03-16 13:41:13 +03:00

Author

Owner

@elangosundar commented on GitHub (Dec 3, 2019):

@liyasthomas can you tried the above reproduce steps.

It is simple ,
you add some raw data in POST method and just on/off the raw input after that you will change method as GET method, now you will check above request parmas.

@elangosundar commented on GitHub (Dec 3, 2019): @liyasthomas can you tried the above reproduce steps. It is simple , you add some raw data in POST method and just on/off the raw input after that you will change method as GET method, now you will check above request parmas.

kerem commented

2026-03-16 13:41:18 +03:00

Author

Owner

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

That's a feature. Actually when you disable the raw input or changed to any other method, payload is stored to the app's state so it could be used next time.

Think of this as: You send a POST request with some payload and have to check it's GET response. So you switched to GET and send another request. Now, if we clear the POST payload, you've to type in all payload again since it is not in app's memory anymore. This is why payload is preserved for using next time.

And don't worry, GET requests won't send payload. It's just for saving the state in your localStorage.

@liyasthomas commented on GitHub (Dec 4, 2019): That's a feature. Actually when you disable the raw input or changed to any other `method`, payload is stored to the app's state so it could be used next time. Think of this as: You send a POST request with some payload and have to check it's GET response. So you switched to GET and send another request. Now, if we clear the POST payload, you've to type in all payload **again** since it is not in app's memory anymore. This is why payload is preserved for using next time. And don't worry, GET requests won't send payload. It's just for saving the state in your `localStorage`.

kerem referenced this issue

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

[PR #145] [MERGED] ⬆️ Bump yargs-parser from 13.1.1 to 14.0.0 #2439