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
4 changes: 2 additions & 2 deletions draft-ietf-httpbis-early-hints.md
View file
Open in desktop
Expand Up @@ -144,8 +144,8 @@ This can happen for example when a caching intermediary generates a 103 (Early H
on the header fields of a stale-cached response, then forwards a 103 (Early Hints) response and a
final response that were sent from the origin server in response to a revalidation request.

Since the nonexistence of a header field within a 103 (Early Hints) response does not indicate the absence of that header field in the final response, a server MAY omit a header field that was included in one 103 (Early Hints) response in the following 103 (Early Hints) responses, even when it is still expected that the header field will be part of the final response.
A client SHOULD NOT consider the disappearance of a header field in the following 103 (Early Hints) responses as an indication that the server has retracted the expectation that the header field will be found in the final response.
Since the nonexistence of a header field within a 103 (Early Hints) response does not indicate the absence of that header field in the final response, a server can omit a header field that was included in one 103 (Early Hints) response in the following 103 (Early Hints) responses, even when it is still anticipated that the header field will be part of the final response.
What a client would expect in the final response is a union of the header fields that were found in the multiple 103 (Early Hints) responses.

# Security Considerations

Expand Down