-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
doc: DEP0066 is slightly incorrect #37641
Labels
doc
Issues and PRs related to the documentations.
feature request
Issues that request new features to be added to Node.js.
good first issue
Issues that are suitable for first-time contributors.
http
Issues or PRs related to the http subsystem.
Comments
benjamingr
added
feature request
Issues that request new features to be added to Node.js.
http
Issues or PRs related to the http subsystem.
labels
Mar 6, 2021
@nodejs/http |
What about |
The issue is with |
mcollina
added
the
good first issue
Issues that are suitable for first-time contributors.
label
Mar 8, 2021
I think when we deprecated |
simov
added a commit
to simov/node
that referenced
this issue
Mar 8, 2021
Trott
pushed a commit
to simov/node
that referenced
this issue
Mar 20, 2021
Fixes: nodejs#37641 PR-URL: nodejs#37660 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
doc
Issues and PRs related to the documentations.
feature request
Issues that request new features to be added to Node.js.
good first issue
Issues that are suitable for first-time contributors.
http
Issues or PRs related to the http subsystem.
📗 API Reference Docs Problem
Location
Affected URL(s):
Description
DEP0066 implies that using
OutgoingMessage.prototype.getHeaderNames()
is equivalent to the now deprecatedOutgoingMessage.prototype._headerNames
property which is not the case.OutgoingMessage.prototype._headerNames
contains a mapping from lowercase to the exact header names that were sent with the request:Where
OutgoingMessage.prototype.getHeaderNames()
returns only lowercase names.The now deprecated
_headerNames
property is useful in http debug logging modules that print the exact header names being sent, as some servers are still picky about those. Not having access to the actual header names will make debugging harder, assuming node still sends the headers as they are sent through thehttp.request
method.Besides the documentation being misleading about this I'd like to know if there is a way to access the headers being sent going forward, since
_headerNames
is now deprecated.The text was updated successfully, but these errors were encountered: