refactor(node)!: reimplement fast headers based on raw headers #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, we were using a proxy view over
IncomingMessage.headers
which was buggy and needing to implement allHeaders
prototype.New implementation uses new lazyInherit mechanism (already adopted for Request/Response) and is based on Node.js lower level
req.rawHeaders
Breaking change: Low level NodeRequestHeaders, NodeResponseHeaders are not exported anymore as might be subject to change and are not much usable externally.