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

clarify multi-103 behavior #380

Merged
merged 8 commits into from Aug 11, 2017
Merged

clarify multi-103 behavior #380

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
bbbcb0e
clarify multi-103 behavior (based on the general rule that the absens…
kazuho Aug 7, 2017
ecb2c7e
clarify the general rule
kazuho Aug 7, 2017
e9bdf4a
explain what a client should expect (rather than explaining what it s…
kazuho Aug 8, 2017
5b054b3
adopt https://lists.w3.org/Archives/Public/ietf-http-wg/2017JulSep/03…
kazuho Aug 11, 2017
641c10e
remove superflous `is`
kazuho Aug 11, 2017
46c1a48
avoid lower-case "may"
kazuho Aug 11, 2017
85d06dc
revert introduction of a separate section
kazuho Aug 11, 2017
2f6f42d
add example
kazuho Aug 11, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
25 changes: 25 additions & 0 deletions draft-ietf-httpbis-early-hints.md
View file
Open in desktop
Expand Up @@ -146,6 +146,31 @@ A server MAY emit multiple 103 (Early Hints) responses with additional header fi
It does not need to repeat the fields that were already emitted, though it doesn't have to exclude them either.
The client can consider any combination of header fields received in multiple 103 (Early Hints) responses when anticipating the list of header fields expected in the final response.

The following example illustrates a series of responses that a server might emit.
In the example, the server uses two 103 (Early Hints) responses to notify the client that it is likely to send three Link header fields in the final response.
Two of the three expected header fields are found in the final response.
The other header field is replaced by another Link header field that contains a different value.

~~~ example
HTTP/1.1 103 Early Hints
Link: </main.css>; rel=preload; as=style

HTTP/1.1 103 Early Hints
Link: </style.css>; rel=preload; as=style
Link: </script.js>; rel=preload; as=script

HTTP/1.1 200 OK
Date: Fri, 26 May 2017 10:02:11 GMT
Content-Length: 1234
Content-Type: text/html; charset=utf-8
Link: </main.css>; rel=preload; as=style
Link: </newstyle.css>; rel=preload; as=style
Link: </script.js>; rel=preload; as=script

<!doctype html>
[... rest of the response body is omitted from the example ...]
~~~

# Security Considerations

Some clients might have issues handling 103 (Early Hints), since informational responses are rarely
Expand Down