| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
|
The test now run through. So I think this one is ready for review. |
Sorry, something went wrong.
|
Are those custom settings passed through the connection/other peer? |
Sorry, something went wrong.
As far as I understand the settings should be sent to the other side of the connection, so for example to the browser. I am currently separated from my development computer until the end of the week, I will then try to fix the problems the automated test showed. |
Sorry, something went wrong.
There was a problem hiding this comment.
This needs to be explained in greater detail.
Sorry, something went wrong.
There was a problem hiding this comment.
This needs to be explained in greater detail.
So more like this:
The key of the object defines the numeric value of the settings type (as defined in the "HTTP/2 SETTINGS" registry established by [RFC7540]) and the values the actual numeric value of the settings. It is only supported for sending SETTINGS. Custom setiings are not supported for the functions retrieving remote and local settings as nghttp2 does not pass unknown HTTP/2 settings to node.js.
Sorry, something went wrong.
There was a problem hiding this comment.
yes
Sorry, something went wrong.
|
Ok, I am back at my development machine. |
Sorry, something went wrong.
|
you can lint with make lint-js-fix 😄 |
Sorry, something went wrong.
Yes, I know, but I checked out node at a commit where it was broken. And I did not find the time to recompile. |
Sorry, something went wrong.
|
I hopefully have fixed all failures by hand. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Hopefully the last correction for CI to work. |
Sorry, something went wrong.
Sorry, something went wrong.
|
I think you pushed way more commits than you should have, there are a few spurious ones. Can you fix it? |
Sorry, something went wrong.
|
Oh you are right. The rebasing went wrong...... |
Sorry, something went wrong.
Currently, node.js http/2 is limited in sending SETTINGs, that are currently implemented by nghttp2. However, nghttp2 has the ability to send arbitary SETTINGs, that are not known beforehand. This patch adds this feature including a fall back mechanism, if a SETTING is implemented in a later nghttp2 or node version. Fixes: nodejs#1337
Test for the http2 setting's custom settings were added.
Add an explanation to the documentation for Http2Settings to explain the usage of customSettings and its limitations. Co-authored-by: James M Snell <jasnell@gmail.com>
|
Ok, I have now force-pushed the branch, with cherry picking the changing commits. I have now to run tests to check, if liniting is ok. |
Sorry, something went wrong.
|
Ok, make lint passed. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
I have no idea, why some of the jobs fail. One fails with "parallel.test-inspector-break-when-eval", which seems to be unrelated to the changes. The other fails with out of memory. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Currently, node.js http/2 is limited in sending SETTINGs, that are currently implemented by nghttp2. However, nghttp2 has the ability to send arbitary SETTINGs, that are not known beforehand. This patch adds this feature including a fall back mechanism, if a SETTING is implemented in a later nghttp2 or node version. Fixes: #1337 PR-URL: #49025 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Currently, node.js http/2 is limited in sending SETTINGs, that are currently implemented by nghttp2. However, nghttp2 has the ability to send arbitary SETTINGs, that are not known beforehand. This patch adds this feature including a fall back mechanism, if a SETTING is implemented in a later nghttp2 or node version. Fixes: #1337 PR-URL: #49025 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
| Back | FazBrowse Home | New Git URL |
This PR implements the ability to send additional HTTP/2 settings with node.js, which are currently not directly implemented with node and the underlying nghttp2 lib. Receiving these settings is not possible, since nghttp2 actively checls for and passes only settings, that it knows. It is currently limited to 10 additional settings.
The intention of this PR is first to get feedback for the used interfacing before progressing further with the PR.
TODOs:
EDIT: Automated tests are added, and will be run soon.... (tested) EDIT2: Test run as part of node's test, which should suffcient.
Related issue
#48962