Postman is sending additional headers in the request
AmitDesai1978 opened this issue · 3 comments
I am finding that postman sends additional request headers to the back end API in addtion to the ones listed in the GUI.
For example
Accept-Encoding: gzip is sent to the back end, even though I havent set it on the UI.
Makes debuging an API very difficult if you cant trust what is being sent to the back end
These headers are appended by Chrome. Once the XHR API opens up (I hope) there will be more control over this. What's your use case? Which headers are making debugging difficult?
I need to debugging gzip behaviour :)
I want to test my web server to see of it correctly responds to the
accept-encoding header
On Tuesday, December 10, 2013, Abhinav Asthana wrote:
These headers are appended by Chrome. Once the XHR API opens up (I hope)
there will be more control over this. What's your use case? Which headers
are making debugging difficult?—
Reply to this email directly or view it on GitHubhttps://github.com//issues/443#issuecomment-30231179
.
Amit Desai
Digital Solutions Architect
Email: amitdesai1978@gmail.com amit.desai@telegraph.co.uk
Mobile: 07970 818007
LinkedIn: http://www.telegraph.co.uk/
http://uk.linkedin.com/in/amitdesai1978
You can try out the Postman proxy as mentioned in the docs here: http://www.getpostman.com/docs/requests