-
Notifications
You must be signed in to change notification settings - Fork 37
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
h2spec #22
Comments
Any progress? |
Not yet. Do you want to help me with this? |
Maybe I will send some pull requests. |
I think |
Yeah Could you please explain what exactly happening in scheduler and why is it causing |
After some debugging I found that GOAWAY frame is encoded and scheduled, and dequeued from scheduler to write queue. Maybe stream closed before actual write to socket. But I failed to fix it anyway, with "dirty hacks" too. |
See: #22 Fixed: 5.1 Stream States × idle: Sends a DATA frame × idle: Sends a RST_STREAM frame × idle: Sends a WINDOW_UPDATE frame 5.1.1 Stream Identifiers × Sends even-numbered stream identifier 5.5 Extending HTTP/2 × Sends an unknown extension frame in the middle of a header block 6.1 DATA × Sends a DATA frame with 0x0 stream identifier 6.4 RST_STREAM × Sends a RST_STREAM frame on a idle stream 6.5.2 Defined SETTINGS Parameters × SETTINGS_ENABLE_PUSH (0x2): Sends the value other than 0 or 1 × SETTINGS_INITIAL_WINDOW_SIZE (0x4): Sends the value above... × SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value below the... × SETTINGS_MAX_FRAME_SIZE (0x5): Sends the value above the... 8.2. Server Push × Sends a PUSH_PROMISE frame
Updated to:
|
Looks like there are many errors when running
h2spec
againstspdy-transport
.The text was updated successfully, but these errors were encountered: