Uh oh!
There was an error while loading. Please reload this page.
http2: add test-http2-date-header.js - #94
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
robertkowalski
commented
May 10, 2017
thanks for your feedback. i found another issue before i am ready to rebase and i am ready for the final review: #99 |
mcollina
commented
May 15, 2017
@robertkowalski any update on this one? |
robertkowalski
commented
May 15, 2017
8a63c8e to
c6f37aeComparerobertkowalski
commented
May 15, 2017
thanks for your help and the friendly nudge @mcollina all is ready now :) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
PR-URL: nodejs#3 Reviewed-By: Fedor Indutny <fedor.indutny@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Allows TLS renegotiation to be disabled per `TLSSocket` instance. Per HTTP/2, TLS renegotiation is forbidden after the initial connection prefix is exchanged.
Squashed rollup of all the progress to this point
PR-URL: nodejs#58 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: nodejs#65 Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Just reading through the code and noticed that the stream event can take headers and flags. Just adding them for readability and asserting the values in the headers and flags. PR-URL: nodejs#71 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
PR-URL: nodejs#78 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#64 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#64 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: nodejs#83 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Currently when compiling the following error is displayed: In file included from /out/Release/obj/gen/node_javascript.cc:6: ../src/env-inl.h:201:7: warning: field 'fs_stats_field_array_' will be initialized after field 'http2_socket_buffer_' [-Wreorder] fs_stats_field_array_(nullptr), ^ In file included from /out/Debug/obj/gen/node_javascript.cc:6: ../src/env-inl.h:201:7: warning: field 'fs_stats_field_array_' will be initialized after field 'http2_socket_buffer_' [-Wreorder] fs_stats_field_array_(nullptr), ^ 1 warning generated. This commit changes the order so that the members appear in the same order in the initializer list. PR-URL: nodejs#85 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This might be an incorrect change but the naming looks to be a little different for these files and wanted to bring it up. Feel free to close if this is indeed correct. PR-URL: nodejs#74 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
These are forbidden by HTTP/2. PR-URL: nodejs#128 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: nodejs#129 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: nodejs#120 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Support the socket/connection getter like require('http') does.
PR-URL: nodejs#130
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>Support the upgrade path from https to http2. PR-URL: nodejs#125 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
* rename functions in docs * add warning against using socket directly * document paddingStrategy / selectPadding * fill in missing details and examples PR-URL: nodejs#132 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: nodejs#134 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Fixes: nodejs#135 PR-URL: nodejs#137 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
jasnell
commented
May 31, 2017
This will need to be rebased :-) |
* tighten up the Http2Stream/Http2Session lifecycle, destroy, and error handling. Some simplification, and more new tests * Eliminate queuing of internal callbacks. Queuing these to fire on the next event loop tick was throwing off timing. Now the js callbacks are called directly as they happen. This will require a bit more finesse on the javascript side (to ensure appropiate timing of destroy/shutdown actions) but that is handled from within the core api impl so users should not be affected. * fix debug output with nghttp2 PR-URL: nodejs#138 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Using `./configure --debug-http2` will enable verbose debug statements from node.js, Using `./configure --debug-nghttp2` will enable verbose debug statements from nghttp2. The two can be used together PR-URL: nodejs#138 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
c6f37ae to
2d62725Comparefixed, but it seems the tests of other http2 functionality are red right now? |
jasnell
commented
Jun 1, 2017
Yeah, will need my current PR to land. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
* Follow the model of the existing http code and pass the headers in to js as an array. Building the array on the native side then converting it to an object on the js side is generally faster than building the object on the native side. This also allows us to eliminate some duplicated checks. * Fill in additional doc details * Work on timeouts PR-URL: nodejs#148 Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
jasnell
commented
Jun 6, 2017
It should work now after a rebase. |
Emit `unknownProtocol` event or silently destroy the socket PR-URL: nodejs#144 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
robertkowalski
commented
Jun 6, 2017
sorry, still doesn't work: |
jasnell
commented
Jun 7, 2017
Interesting... the only failure I'm getting is the socketHangUp which is fixed by my other PR. What platform are you on? |
2d62725 to
8faa0d1Comparejasnell
commented
Jun 7, 2017
@mcollina ... can you test to see if you see the same issues @robertkowalski is getting? |
I'm getting: EDIT: on |
b271202 to
734ad72Compare
This is porting the http1 test https://github.com/nodejs/http2/blob/98e54b0bd4854bdb3e2949d1b6b20d6777fb7cde/test/parallel/test-http-date-header.js to http2.
I found several issues (see comments in test):
[ ]
req.urlis undefined, due to missing accessor for url[ ]
req.headersis undefined[ ]
req.getHeader('date')crashes with:For the header issues, it seems
stream[kHeaders]is returningundefined.Stacktrace:
It seems
stream[kHeaders]is returningundefinedCode for
req.headersandreq.getHeader, note the use ofstream[kHeaders]:So far I haven't found out why exactly
stream[kHeaders]does not return the right value and need help with that.UPDATE: all issues fixed.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
http2