You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Response object does not have response.headers #71
The response object in Node's http module (an instance of http.IncomingMessage) exposes the response headers via response.headers (and notresponse.getHeader()). This module does the opposite - http-browserify's response object has response.getHeader() (and notresponse.headers).
The response object should be changed to match Node core's http module by adding .headers and removing .getHeader().
Sorry. It looks like the response object does indeed have .headers. This is just not documented in the readme. It also does have .getHeader() (which is documented in the readme) even though the node http module does not - but I guess that's ok.
Activity
parshap commentedon Oct 31, 2014
Sorry. It looks like the response object does indeed have
.headers. This is just not documented in the readme. It also does have.getHeader()(which is documented in the readme) even though the node http module does not - but I guess that's ok.Update documentation to match node http module
parshap commentedon Oct 31, 2014
Sent a pull request to change the documentation - see #72.
Closing this now, but you may want to remove
response.getHeader()in the future to be strictly equivalent to node's http module.Update documentation to match node http module