Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add configuration to disable temporary headers #2689

Open
adkathuria opened this issue Feb 9, 2017 · 12 comments
Open

Add configuration to disable temporary headers #2689

adkathuria opened this issue Feb 9, 2017 · 12 comments

Comments

@adkathuria
Copy link

@adkathuria adkathuria commented Feb 9, 2017

I see the response headers as Content-Encoding: gzip even without specifying the Accept-Encoding: gzip as the input. Is it the Chrome code that inserts the header "Accept-Encoding: gzip" during the request?

@prashantagarwal

This comment has been minimized.

Copy link

@prashantagarwal prashantagarwal commented Sep 22, 2017

@adkathuria are you on Postman native app or Chrome app. Also can you provide me with the version number of your Postman app.

@ddecesare

This comment has been minimized.

Copy link

@ddecesare ddecesare commented Apr 9, 2018

I know this issue was closed but I'm seeing the same issue. I'm using Postman native app (version Postman for Windows Version 6.0.10 win32 10.0.16299 / x64).

It appears Postman is automatically sending the header "accept-encoding: gzip, deflate". I noticed this because while that worked for Wildfly 8, it does not work for Wildfly 11. Wildfly 11 needs the header to look like "Accept-Encoding: application/gzip".

When I manually add "Accept-Encoding: application/gzip" to the header, the default Postman header is no longer sent.

@MaxRev-Dev

This comment has been minimized.

Copy link

@MaxRev-Dev MaxRev-Dev commented Jun 23, 2018

image
+1 Same issue. Postman handles decoding only in chrome app

@cabrinoob

This comment has been minimized.

Copy link

@cabrinoob cabrinoob commented Sep 12, 2018

Have the same pb here with postman native app 6.3.0.
Postman seems to send Accept-Encoding: application/gzinp, deflate and I have an error message "Could not get any response".

The same request works fine with fiddler because fiddler does not add any accept-encoding header silently.

@IanKemp

This comment has been minimized.

Copy link

@IanKemp IanKemp commented Jan 8, 2019

How is this incredibly important bug not addressed yet? If I send a request I expect it to have the headers I explicitly set or allowed to be sent via the program's options, I do NOT expect additional headers like accept-encoding (name is a violation of the HTTP spec BTW) to be appended! Doing so breaks the whole point of an app that is supposed to allow for testing of HTTP requests!

Postman for Windows
Version 6.6.1
win32 10.0.17134 / x64

@IanKemp

This comment has been minimized.

Copy link

@IanKemp IanKemp commented Jan 8, 2019

To get around this and essentially "unset" the unwanted accept-encoding header, manually specify Accept-Encoding: identity (see MDN).

@Luthien-in-edhil

This comment has been minimized.

Copy link

@Luthien-in-edhil Luthien-in-edhil commented Mar 4, 2019

That's a big +1 from me.

I was unaware that Postman added this header, which had me stumped for quite some time while trying to figure out how to enable HTTP gzip compression on a Solr connection.

I know, I only have myself to blame for missing this cause for the weird behaviour that I saw, but still ... as IanKemp also says: it's not something that you would expect from an application that is specifically intended to test HTTP connections with.

So, just that you are aware that there actually exist use cases that are about the effect of adding the Accept-Encoding header ;)

Until it is fixed, at least add a message to the startup screen, for instance "WARNING! Postman adds hidden headers to your request!" instead of that "enabling warp engines" waggery (although I haven't seen that in a while).

@codenirvana

This comment has been minimized.

Copy link
Member

@codenirvana codenirvana commented May 13, 2019

@Luthien-in-edhil In the latest version of the Postman app, all these headers are visible under the "Temporary Headers" section.

@codenirvana

This comment has been minimized.

Copy link
Member

@codenirvana codenirvana commented May 13, 2019

Doing so breaks the whole point of an app that is supposed to allow for testing of HTTP requests!

@IanKemp Agree, we are planning to add a configuration which turns off all the auto header injection.

Updated the issue title.

@codenirvana codenirvana changed the title Content-Encoding: gzip even without Accept-Encoding: gzip, deflate being sent Add configuration to disable temporary headers May 13, 2019
@saswatds saswatds added this to Pending triage in Runtime Triage and Development via automation Jun 18, 2019
@saswatds saswatds moved this from Pending triage to Later in Runtime Triage and Development Jun 18, 2019
@lovelock

This comment has been minimized.

Copy link

@lovelock lovelock commented Aug 24, 2019

most important is, because postman sends a request with that header, when the request code is copied from postman and then paste to terminal to run with curl, it would crash and I have to remove the gzip header manually.

@VicKetchup

This comment has been minimized.

Copy link

@VicKetchup VicKetchup commented Nov 25, 2019

Linking the discussion from community forums, as that is what comes up on Google first for the issue: https://community.getpostman.com/t/disable-temporary-headers/5271

@PylotLight

This comment has been minimized.

Copy link

@PylotLight PylotLight commented Jan 15, 2020

This was still being considered in mid 2019 is that right?
Is this setting still being worked on?
Look at this mess generated by the temporary headers:
sessionid=e798ac6bbb62db95b9f3bc4a69e338f0; sessionid=7dbd00b00a4b418b5ab3c4555a93835c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.