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.

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

Add note about 103 and HTTP/2 #9563

Merged
merged 4 commits into from
Aug 1, 2023
Merged
Changes from all commits
Commits
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
7 changes: 7 additions & 0 deletions source
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://httpwg.org/specs/rfc8297.html#security-considerations">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 Expand Up @@ -138820,6 +138826,7 @@ INSERT INTERFACES HERE
Avi Drissman,
Axel Dahmen,
방성범 (Bang Seongbeom), <!-- bangseongbeom on GitHub -->
Barry Pollard, <!-- tunetheweb on GitHub -->
Ben Boyle,
Ben Godfrey,
Ben Golightly, <!-- golightlyb on GitHub -->
Expand Down