[GH-ISSUE #57] Request Headers #22

Closed
opened 2026-03-16 12:49:10 +03:00 by kerem · 5 comments
Owner

Originally created by @JockDaRock on GitHub (Aug 25, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/57

Is your feature request related to a problem? Please describe.
Would like to be able to add custom request headers to requests before sending and control headers that are sent.

Describe the solution you'd like
A section the has request headers where you can control and add headers to be sent with API request

Originally created by @JockDaRock on GitHub (Aug 25, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/57 **Is your feature request related to a problem? Please describe.** Would like to be able to add custom request headers to requests before sending and control headers that are sent. **Describe the solution you'd like** A section the has request headers where you can control and add headers to be sent with API request
kerem 2026-03-16 12:49:10 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

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

That would be great. Lets discuss its scope here and will try to implement it.

<!-- gh-comment-id:524602244 --> @liyasthomas commented on GitHub (Aug 25, 2019): That would be great. Lets discuss its scope here and will try to implement it.
Author
Owner

@brandonros commented on GitHub (Aug 25, 2019):

One of my biggest gripes with Postman is how it tries to handle the Cookie header for you (based off of the Set-Cookie response)

It tries to blend its own internal cookie jar with a sometimes explicitly set Cookie header.

I'd say, make the cookie jar functionality an option, therefore allowing the user to "break out" and handle the Cookie header on their own, if needed.

<!-- gh-comment-id:524634065 --> @brandonros commented on GitHub (Aug 25, 2019): One of my biggest gripes with Postman is how it tries to handle the `Cookie` header for you (based off of the Set-Cookie response) It tries to blend its own internal cookie jar with a sometimes explicitly set Cookie header. I'd say, make the cookie jar functionality an option, therefore allowing the user to "break out" and handle the Cookie header on their own, if needed.
Author
Owner

@brandonros commented on GitHub (Aug 25, 2019):

Scope:

UI presents the same UI for "parameters" to manage key value pairs of string (headerName) -> string (header value). Pass them along as request header. Voila. 🎉

Where it gets tricky is.... do you want to support cases where the "key" is not unique? example:

curl -H 'foo: 1' -H 'foo: 2'

I don't know why people would ever do this, but I know for darn sure that TypeScript complains if I try to treat a request header in node.js as a string instead of string | string[].

I'd vote no, don't support that. :)

<!-- gh-comment-id:524634213 --> @brandonros commented on GitHub (Aug 25, 2019): Scope: UI presents the same UI for "parameters" to manage key value pairs of string (headerName) -> string (header value). Pass them along as request header. Voila. 🎉 Where it gets tricky is.... do you want to support cases where the "key" is not unique? example: `curl -H 'foo: 1' -H 'foo: 2'` I don't know why people would ever do this, but I know for darn sure that TypeScript complains if I try to treat a request header in node.js as a string instead of `string | string[]`. I'd vote no, don't support that. :)
Author
Owner

@JacobAnavisca commented on GitHub (Aug 27, 2019):

Just made a pull for this https://github.com/liyasthomas/postwoman/pull/68

Also added orange if that's okay for another color.

<!-- gh-comment-id:525129129 --> @JacobAnavisca commented on GitHub (Aug 27, 2019): Just made a pull for this https://github.com/liyasthomas/postwoman/pull/68 Also added orange if that's okay for another color.
Author
Owner

@liyasthomas commented on GitHub (Aug 27, 2019):

#68 fixes this issue hence closing

<!-- gh-comment-id:525137170 --> @liyasthomas commented on GitHub (Aug 27, 2019): #68 fixes this issue hence closing
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#22
No description provided.