-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
103 Early Hints leads to endless wait for headers #7936
Comments
Yep - there is a race condition, and when it blocks we are treating them as trailers. I'll try to find the right fix. |
I could reproduce with 5.x, so if blocked use that until a release. |
I haven't reproduced on 5.x, and that server now doesn't return a 103. I have some alternate servers, but I think this particular error relates to a 103 and then a response without a body. https://early-hints.fastlylabs.com/test.png So I don't have a good repro to confirm the fix. |
@swankjesse I think I understand why it's only happening when the response body is empty.
|
Minimal fix in #8054 |
Steps to reproduce.
Execute the code snipper below multiple times (it reproduces in ~ 1/4 of runs) using
v4.11.0
The main thread hangs forever in waitForIo of Http2Stream#takeHeaders.
I investigated a bit, and it looks like it only happens for
103 Early Hints
response codes (inside the CallServerInterceptor#shouldIgnoreAndWaitForRealResponseif
).Also, I figured out that the Http2Stream.StreamTimeout is called after some time, but it does not unblock the main thread.
The text was updated successfully, but these errors were encountered: