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
3 changes: 3 additions & 0 deletions draft-ietf-httpbis-early-hints.md
View file
Open in desktop
Expand Up @@ -105,6 +105,9 @@ Aside from performance optimizations, such evaluation of the 103
client MUST NOT interpret the 103 (Early Hints) response header fields as if they applied to
the informational response itself (e.g., as metadata about the 103 (Early Hints) response).

A server MAY use a 103 (Early Hints) response to indicate only some of the header fields that are expected to be found in the final response.
A client SHOULD NOT interpret the nonexistence of a header field in a 103 (Early Hints) response as a speculation that the header field is unlikely to be part of the final response.

The following example illustrates a typical message exchange that involves a 103 (Early Hints) response.

Client request:
Expand Down