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

settings parameter to indicate support for CACHE_DIGEST #340

Merged
merged 5 commits into from May 25, 2017
Merged

settings parameter to indicate support for CACHE_DIGEST #340

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0ac82a5
settings parameter to indicate support for CACHE_DIGEST
kazuho Apr 28, 2017
75f9150
clarify the settings of the connections that can be reused
kazuho May 1, 2017
db84551
Merge branch 'master' into kazuho/settings-cache-digest
mnot May 25, 2017
28f4bc9
Merge branch 'master' into kazuho/settings-cache-digest
mnot May 25, 2017
11cab73
missed one
mnot May 25, 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
2 changes: 1 addition & 1 deletion draft-ietf-httpbis-cache-digest.md
View file
Open in desktop
Expand Up @@ -285,7 +285,7 @@ Rest of the bits MUST be ignored and MUST be left unset when sending.

The initial value of the parameter is zero (0x0) meaning that the server is not interested in seeing a CACHE_DIGEST frame.

Some underlying transports allow the server's first flight of application data to reach the client at around the same time when the client sends it's first flight data. When such transport (e.g., TLS 1.3 {{I-D.ietf-tls-tls13}} in full-handshake mode) is used, a client can postpone sending the CACHE_DIGEST frame until it receives a SETTINGS_CACHE_DIGEST settings value.
Some underlying transports allow the server's first flight of application data to reach the client at around the same time when the client sends it's first flight data. When such transport (e.g., TLS 1.3 {{I-D.ietf-tls-tls13}} in full-handshake mode) is used, a client can postpone sending the CACHE_DIGEST frame until it receives a ACCEPT_CACHE_DIGEST settings value.

When the underlying transport does not have such property (e.g., TLS 1.3 in 0-RTT mode), a client can reuse the settings value found in previous connections to that origin {{RFC6454}} to make assumptions.

Expand Down