-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Support Http Response 103 (Early Hints) #8057
Comments
I wonder how a The only difference I can see is that Server push has been removed from HTTP/3, and a Furthermore, there is no API on the server to send a We need to consider whether to add a "send informational response" API in Jetty 12. |
I think a 103 is very similar to our current support of 102 PROCESSING. We currently allow a However, I'm unsure if 102 or 103 are handled completely by http>=2 We also need to consider if we want optional or mandatory Expect headers. |
Chrome 95 was the first version to support 103 Early Hints. https://chromium.googlesource.com/chromium/src/+/master/docs/early-hints.md Fastly opened support in Nov 2020. Cloudfare opened support in Sep 2021 |
Added test harness for intermediary responses.
I've opened a branch for this and started by adding a better test for 100 and 102 responses. These work for all protocols. |
Implemented 103 early hint, but is failing for HTTP>=2
Added test harness for intermediary responses.
Implemented 103 early hint, but is failing for HTTP>=2
Fixed flake. @sbordet please review this commit!
Improved implementation on the client-side. Introduced HttpStatus.isInterim() for 1XX codes that are not 101. Signed-off-by: Simone Bordet <[email protected]>
Co-authored-by: Ludovic Orban <[email protected]> Co-authored-by: Simone Bordet <[email protected]>
@joakime can you pass this on to the user |
Target Jetty version(s)
10+
Enhancement Description
What would it take to have Jetty support response code 103 (Early Hints)?
The text was updated successfully, but these errors were encountered: