-
Notifications
You must be signed in to change notification settings - Fork 63
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
goaway when talking to Cloudflare #129
Comments
Could you print a "frame trace"? That's interesting indeed. |
Let me see if I can repro... I sort of trashed all that code now. |
Okay first problem. If headers is an empty hash, it fails:
|
Uh, actually hold on, let me check that. |
Yes,
fails. |
Sending headers twice fails with:
|
That's indeed interesting. Let me have a look at it later. As a sidenote, is this an issue only with cloudflare endpoints? Or overall? |
It worked with internal requests, i.e. async-http client and server seemed fine. Here is a full transaction/example:
|
CloudFlare might just have a broken implementation of HTTP/2? |
I'd assume the opposite. They see more daily usage than this lib. It's either misusage or a bug, most likely |
could you share the URL you tested this against? I've tested this against google, and it worked. |
ok, tested it against https://www.cloudflare.com, and reproduced your problem. It seems to be that their stack doesn't support CONTINUATION frames(?) |
/cc @jgrahamc for tips and guidance from Cloudflare side :-) |
Any update on this, or should we close as a bug with Cloudflare? |
According to my understanding of the spec, sending multiple header frames is invalid. That being said, it should be possible to use it for trailing headers, but that's not something I tested. |
When I tried to send the headers frame twice, I received
goaway
.I ended up doing this:
However, is there some reason why sending headers twice would be a problem? After my discussion with @HoneyryderChuck I thought it was ok (with
end_headers:false
).The text was updated successfully, but these errors were encountered: