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
H2 Early Hints cannot be used with response streaming #32329
Comments
Might be related PRs:
|
Anyone? |
Oops this was using `v` instead of `vs` here which means it couldn't have been working. Ref rails/rails#32329 and https://github.com/puma/puma/pull/1403/files#r176663645
Oops this was using `v` instead of `vs` here which means it couldn't have been working. Ref rails/rails#32329 and https://github.com/puma/puma/pull/1403/files#r176663645
Ping... |
Pong... |
Did you check if the linked PR fixed the issue? |
If you are talking about If you are talking about
|
This issue has been automatically marked as stale because it has not been commented on for at least three months. |
I think this is still a valid bug |
I agree this is a bug, but I think it's in the Puma side. (cc @eileencodes @schneems) While we could remember that the response has started so there's no benefit to trying to send early hints, I think it's on Puma to actively ignore any hints it gets, because it owns the output stream that they're messing up. I'm sure they'd love a pull request to fix it, if you're interested. (Specifically, I think the contents of the |
This issue has been automatically marked as stale because it has not been commented on for at least three months. |
Steps to reproduce
puma --early-hints
Expected behavior
The response should NOT emit Early Hint lines during rendering with response streaming enabled
Actual behavior
Illegal or missing hexadecimal sequence in chunked-encoding
Probably due to emission of Early Hint lines
System configuration
Rails version:
5.2.0.rc2
Ruby version:
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin16]
CURL output
Response Streaming Disabled
Response Streaming Enabled
The text was updated successfully, but these errors were encountered: