-
Notifications
You must be signed in to change notification settings - Fork 39
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
Sent headers (feature request) #1
Comments
Can you give an example? Are you talking about the display of Response headers? The response view should show all of the response headers as returned from the server. |
The latter, in a manner similar to how they're shown in the Response pane. Hilariously I only just now realized that the panes have groupbox controls naming them. Sorry for ambiguity if there was any :/ |
Ok I gotcha. Those other headers get added somewhere down the line by On Mon, Nov 10, 2014 at 5:24 PM, Anthony Garcia notifications@github.com
|
I actually tried poking around the MDN to see if I could give a suggestion for this rather than just "I want this" but couldn't find much besides the SDK request class. One possibility is that the headers prop gets populated with the builtin headers it sends after the request is actually made. Not sure. Something to experiment with though. |
The ability to display what exact request headers are being sent is indeed missing. |
I'm really liking this extension. It's a hell of a lot better than RESTClient that's for sure. One of the very few things that it's missing though is a display of what (non-custom) headers were sent in a manner similar to the headers shown in the response pane. Seeing such things is very useful for the servers that have conditional responses based on things like user agent and things of that nature.
Perhaps a combined display of both the non-custom and custom headers that reflects the layout of the response pane?
The text was updated successfully, but these errors were encountered: