[GH-ISSUE #167] Content-Type is always set to application/x-www-form-urlencoded #66

New issue

Closed

opened 2026-03-16 13:07:43 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 13:07:43 +03:00

Owner

Originally created by @davidyscott on GitHub (Sep 25, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/167

Describe the bug
Regardless of what I select from the Content Type dropdown, requests are actually sent with the header "Content-Type: application/x-www-form-urlencoded".

To Reproduce
Steps to reproduce the behavior:

Open Postwoman and your browser's Network Tools
Make a POST or PUT request with Content Type of "application/json" selected
Observe that the request was actually sent with the header "Content-Type: application/x-www-form-urlencoded"

Expected behavior
The correct Content-Type header is sent.

Originally created by @davidyscott on GitHub (Sep 25, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/167 **Describe the bug** Regardless of what I select from the Content Type dropdown, requests are actually sent with the header "Content-Type: application/x-www-form-urlencoded". **To Reproduce** Steps to reproduce the behavior: 1. Open Postwoman and your browser's Network Tools 1. Make a POST or PUT request with Content Type of "application/json" selected 1. Observe that the request was actually sent with the header "Content-Type: application/x-www-form-urlencoded" **Expected behavior** The correct Content-Type header is sent.

kerem

2026-03-16 13:07:43 +03:00

closed this issue
added the
question

need information
labels

kerem commented

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

Author

Owner

@liyasthomas commented on GitHub (Sep 25, 2019):

I failed to reproduce this issue

@liyasthomas commented on GitHub (Sep 25, 2019): I failed to reproduce this issue

kerem commented

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

Author

Owner

@AndrewBastin commented on GitHub (Sep 25, 2019):

I tested the behavior both from the server and client side, the content-type header seems to be sent fine.

@AndrewBastin commented on GitHub (Sep 25, 2019): I tested the behavior both from the server and client side, the content-type header seems to be sent fine.

kerem commented

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

Author

Owner

@davidyscott commented on GitHub (Sep 25, 2019):

😕 I can't repro it anymore either. Probably some sort of user error!!

@davidyscott commented on GitHub (Sep 25, 2019): :confused: I can't repro it anymore either. Probably some sort of user error!!

kerem commented

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

Author

Owner

@flleeppyy commented on GitHub (Mar 16, 2024):

Hiya, I'm having this issue. I'm only sending query parameters. My body is set to none, yet in the request sent by Hoppscotch, the content type is set to application/x-www-form-urlencoded

@flleeppyy commented on GitHub (Mar 16, 2024): Hiya, I'm having this issue. I'm only sending query parameters. My body is set to none, yet in the request sent by Hoppscotch, the content type is set to `application/x-www-form-urlencoded` ![image](https://github.com/hoppscotch/hoppscotch/assets/18307183/3880c6ac-0037-4e50-bc0d-4c4b578322bf) ![image](https://github.com/hoppscotch/hoppscotch/assets/18307183/d7107db6-6e53-4fff-8b47-6afffe81a627)