Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add note about 103 and HTTP/2 #9563

Merged
merged 4 commits into from
Aug 1, 2023
Merged

Add note about 103 and HTTP/2 #9563

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5c0f8fa
Add note about 103 and HTTP/2
tunetheweb Jul 27, 2023
a7477d5
Remove erroneous bracket
tunetheweb Jul 27, 2023
5bc4f2d
Add to acknowledgements
tunetheweb Jul 31, 2023
c9b6e39
Change the URL to httpwg.org
domenic Aug 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions source
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15791,6 +15791,12 @@ interface <dfn interface>HTMLLinkElement</dfn> : <span>HTMLElement</span> {
<span data-x="concept-response">response</span> with a 103 status code before serving the final
<span data-x="concept-response">response</span>.<ref spec=RFC8297></p>

<p class="note">For compatibility reasons
<a href="https://www.rfc-editor.org/rfc/rfc8297#section-3">it is recommended</a> to only send
early hints responses over HTTP/2 or later, unless the client is known to handle informational
responses correctly. Despite this, the examples below use HTTP/1.1-style notation as per usual
convention.</p>

<div class="example">
<p>For example, given the following sequence of responses:</p>
<pre>103 Early Hint
Expand Down