| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This would change the behavior for non-compat mode also, which is not ideal. The check should be done in compat.js rather than in util.js
Sorry, something went wrong.
|
Ok. |
Sorry, something went wrong.
There was a problem hiding this comment.
This is unfortunately not the right approach. I've left some comments.
Sorry, something went wrong.
Sorry, something went wrong.
|
What about this PR, it is waiting for approval long time. |
Sorry, something went wrong.
|
Hi @sagitsofan , I was just a passer by, similar to you and just had a comment; I don't have the ability to move this further along and eventually merge, sorry. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
@jasnell @apapirovski can you check again?
Sorry, something went wrong.
|
@sagitsofan can you please update the title/description on the PR to something more related the actual change? |
Sorry, something went wrong.
Sorry, something went wrong.
|
@mcollina i updated the title and description and fix the conflicts |
Sorry, something went wrong.
|
@jasnell @apapirovski Can you please review? |
Sorry, something went wrong.
|
Can you please add a unit test? |
Sorry, something went wrong.
Ignoring the connection header and disable the `ERR_HTTP2_INVALID_CONNECTION_HEADERS` error. Added a warning log on the compatibility. Fixes: nodejs#23748
Sorry, something went wrong.
There was a problem hiding this comment.
The test should verify if the warning is emitted.
Sorry, something went wrong.
|
@mcollina, I have verified that the warning is emitted and also i am making sure that adding the connection into the header is not throwing any exception. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Thanx. |
Sorry, something went wrong.
| if (name !== constants.HTTP2_HEADER_CONNECTION) | ||
| return true; | ||
| else | ||
| return value === 'trailers'; |
There was a problem hiding this comment.
Nit: this could be simplified to:
return name !== constants.HTTP2_HEADER_CONNECTION ||
value === 'trailers';
Sorry, something went wrong.
Sorry, something went wrong.
|
Landed in 8c597df 🎉 I took the liberty to improve the commit message and addressed my nit while landing. |
Sorry, something went wrong.
When using the compatibility API the connection header is from now on ignored instead of throwing an `ERR_HTTP2_INVALID_CONNECTION_HEADERS` error. This logs a warning in such case to notify the user about the ignored header. PR-URL: nodejs#23908 Fixes: nodejs#23748 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
When using the compatibility API the connection header is from now on ignored instead of throwing an `ERR_HTTP2_INVALID_CONNECTION_HEADERS` error. This logs a warning in such case to notify the user about the ignored header. PR-URL: #23908 Fixes: #23748 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
When using the compatibility API the connection header is from now on ignored instead of throwing an `ERR_HTTP2_INVALID_CONNECTION_HEADERS` error. This logs a warning in such case to notify the user about the ignored header. PR-URL: #23908 Fixes: #23748 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
When using the compatibility API the connection header is from now on ignored instead of throwing an `ERR_HTTP2_INVALID_CONNECTION_HEADERS` error. This logs a warning in such case to notify the user about the ignored header. PR-URL: #23908 Fixes: #23748 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
lib: http2 compatibility connection header
When adding the connection header into
http2 response, an ERR_HTTP2_INVALID_CONNECTION_HEADERS
error is thrown.
This PR is ignoring the connection header and disable the
ERR_HTTP2_INVALID_CONNECTION_HEADERS error.
A new warning log is emitted on the compatibility.
Fixes: #23748
Checklist