-
Notifications
You must be signed in to change notification settings - Fork 30k
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
http2 - modifying compat req pseudo headers #15312
Comments
Thanks for the report @ronag! It looks like we might need to specifically protect url & method. |
After thinking about this a bit longer, I'm not this can be protected in a way that's satisfactory. In h2, url & method are both a part of the headers unlike in http1. While the goal is to be as compatible with the http1 API as possible, I think there are going to be areas where the differences will come through a little bit. If someone is deleting all headers then that's probably outside of our control. @mcollina Any thoughts? As I see this, |
IMHO this needs to be documented, we cannot do much about it. cc @jasnell. |
Yeah, I agree. Protecting those headers is certainly possible but not without a significant cost to performance that just would not be worth it. Documenting would be best. |
PR-URL: #17329 Fixes: #15312 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Timothy Gu <timothygu99@gmail.com>
PR-URL: #17329 Fixes: #15312 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Timothy Gu <timothygu99@gmail.com>
PR-URL: #17329 Fixes: #15312 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Timothy Gu <timothygu99@gmail.com>
PR-URL: #17329 Fixes: #15312 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Timothy Gu <timothygu99@gmail.com>
PR-URL: #17329 Fixes: #15312 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Jon Moss <me@jonathanmoss.me> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Timothy Gu <timothygu99@gmail.com>
When modifying a compat request headers some properties that depend on pseudo headers stop working. I'm not sure if this would count as compat breaking?
e.g.
@apapirovski
The text was updated successfully, but these errors were encountered: