http: unify the header treatment #46395
Labels
feature request
Issues that request new features to be added to Node.js.
Comments
climba03003
added
the
feature request
|
I will work on this, opening a PR soon |
nodejs-github-bot
pushed a commit
that referenced
this issue
Feb 21, 2023
PR-URL: #46528 Fixes: #46395 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
targos
pushed a commit
that referenced
this issue
Mar 13, 2023
PR-URL: #46528 Fixes: #46395 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
danielleadams
pushed a commit
that referenced
this issue
Apr 11, 2023
PR-URL: #46528 Fixes: #46395 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Robert Nagy <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the problem this feature will solve?
This issue is similar to #42579.
We know that the header serialization will be treat differently when the header of
Transfer-Encoding: chunkedexists or not.Being two different behavior for serialize the header is causing problem if people do not know how it works.
So, here is an ask for unify the behavior between two.
Related fastify/fastify-reply-from#287
cc @SimenB @mcollina @ShogunPanda
What is the feature you are proposing to solve the problem?
It should either throw with proper error or convert to
latin1in all case.I would prefer throwing with an proper explanation.
What alternatives have you considered?
Always check in user-land code, but it is problematic and easily to forgot.
The text was updated successfully, but these errors were encountered: