starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #2828] [bug]: GET Request not using Content-Type application/json Header #910

New issue

Closed

opened 2026-03-16 17:38:40 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 17:38:40 +03:00

Owner

Originally created by @MatheusGrilo on GitHub (Oct 27, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2828

Is there an existing issue for this?

I have searched the existing issues

Current behavior

My JSON on Body do not send when I use GET method (with and without Header modification):

My console.log(req.body) and everything I want on body:

Tested on Google Chrome's App and on Hoppscotch.io itself, also tried to remove <<baseUrl>> with no success. Tested on localhost and on Heroku.
Works fine with Insomnia as you can see bellow:

My console.log(req.body) and everything I want on body with Insomnia:

Steps to reproduce

Use GET Method and try to send a Json Body.
Get undefined as result.

Environment

Production

Version

Local

Originally created by @MatheusGrilo on GitHub (Oct 27, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2828 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current behavior My JSON on Body do not send when I use GET method (with and without Header modification): ![image](https://user-images.githubusercontent.com/7491570/198163433-49bd2487-1c1b-46ae-8be8-1cdcdc3e354b.png) ![image](https://user-images.githubusercontent.com/7491570/198162743-e2b4c215-8771-4d96-a32a-972e50b07868.png) ![image](https://user-images.githubusercontent.com/7491570/198162762-f367931c-1d2e-4c4a-8163-bfec598344f7.png) My console.log(req.body) and everything I want on body: ![image](https://user-images.githubusercontent.com/7491570/198162888-f95fc8cd-a81a-4c03-a1ae-927b08b93f45.png) Tested on Google Chrome's App and on Hoppscotch.io itself, also tried to remove `<<baseUrl>>` with no success. Tested on localhost and on Heroku. Works fine with Insomnia as you can see bellow: ![image](https://user-images.githubusercontent.com/7491570/198162723-8fc19d0f-26e4-4d49-b536-7eec69d51a45.png) ![image](https://user-images.githubusercontent.com/7491570/198163377-230057e4-8f15-4deb-b4a0-6bbd9a1f4ded.png) My console.log(req.body) and everything I want on body with Insomnia: ![image](https://user-images.githubusercontent.com/7491570/198162954-88ccfac2-05c4-4800-bdca-6072562b0c95.png) ### Steps to reproduce Use GET Method and try to send a Json Body. Get **undefined** as result. ### Environment Production ### Version Local

kerem

2026-03-16 17:38:40 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-16 17:38:56 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Oct 27, 2022):

Due to implementation limitations of the browser, I don't think we will be able to support/implement it directly.
Along with that, sending a body on GET is generally an undefined behaviour in the HTTP spec.

Welcoming discussions on this.

@AndrewBastin commented on GitHub (Oct 27, 2022): Due to implementation limitations of the browser, I don't think we will be able to support/implement it directly. Along with that, sending a body on GET is generally an undefined behaviour in the HTTP spec. Welcoming discussions on this.

kerem commented

2026-03-16 17:39:01 +03:00

Author

Owner

@MatheusGrilo commented on GitHub (Nov 5, 2022):

Okay, I will accept that as an answer since I won't use this in production, and was only using in development. Was just an idea since it's possible for tests, but not a real thing.

@MatheusGrilo commented on GitHub (Nov 5, 2022): Okay, I will accept that as an answer since I won't use this in production, and was only using in development. Was just an idea since it's possible for tests, but not a real thing.

kerem commented

2026-03-16 17:39:06 +03:00

Author

Owner

@thomas-frantz commented on GitHub (Oct 3, 2023):

Due to implementation limitations of the browser, I don't think we will be able to support/implement it directly. Along with that, sending a body on GET is generally an undefined behaviour in the HTTP spec.

Welcoming discussions on this.

The only problem with this is when we can't control the APIs. I develop our own company API, and I can do that according to the spec just fine. But I can't control the various other vendors and customers APIs we integrate with who don't do this, many of which do use a body on GET requests. Which essentially makes this unusable for us, unless I'm missing something.

@thomas-frantz commented on GitHub (Oct 3, 2023): > Due to implementation limitations of the browser, I don't think we will be able to support/implement it directly. Along with that, sending a body on GET is generally an undefined behaviour in the HTTP spec. > > Welcoming discussions on this. The only problem with this is when we can't control the APIs. I develop our own company API, and I can do that according to the spec just fine. But I can't control the various other vendors and customers APIs we integrate with who don't do this, many of which do use a body on GET requests. Which essentially makes this unusable for us, unless I'm missing something.

kerem referenced this issue

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

[PR #910] [CLOSED] Add Runme button to demonstrate the latest version of application #2932