Remove Accept-CH-Lifetime #878
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Based on discussion at IETF 105, removing explicit lifetime in favor of implicit opt-in registration and persistence.
yoavweiss
approved these changes
Jul 25, 2019
|
|
||
| Client Hints mitigate the performance concerns by assuring that clients will only send the request headers when they're actually going to be used, and the privacy concerns of passive fingerprinting by requiring explicit opt-in and disclosure of required headers by the server through the use of the Accept-CH response header. | ||
|
|
||
| This document defines the Client Hints infrastructure, a framework that enables servers to opt-in to specific proactive content negotiation features, which will enable them to adapt their content accordingly. However, it does not define any specific features that will use that infrastructure. Those features will be defined in their respective specifications. | ||
|
|
||
| This document does not supersede or replace the User-Agent header field. Existing device detection mechanisms can continue to use both mechanisms if necessary. By advertising user agent capabilities within a request header field, Client Hints allow for cache friendly and proactive content negotiation. |
martinthomson
approved these changes
Jul 29, 2019
Co-Authored-By: Martin Thomson <martin.thomson@gmail.com>
sideshowbarker
added a commit
to w3c/browser-compat-data
that referenced
this pull request
May 10, 2021
httpwg/http-extensions#878 removed the Accept-CH-Lifetime HTTP header from the Client Hints spec, and it’s not part of any other spec — so this change marks it deprecated and standard_track:false.
sideshowbarker
added a commit
to mdn/content
that referenced
this pull request
May 10, 2021
httpwg/http-extensions#878 removed the Accept-CH-Lifetime HTTP header from the Client Hints spec, and it’s not part of any other spec — so this change marks it deprecated and standard_track:false. Related BCD change: mdn/browser-compat-data#10414
sideshowbarker
added a commit
to mdn/content
that referenced
this pull request
May 10, 2021
httpwg/http-extensions#878 removed the Accept-CH-Lifetime HTTP header from the Client Hints spec, and it’s not part of any other spec — so this change adds Deprecated and Non-standard headers to the Accept-CH-Lifetime article. Related BCD change: mdn/browser-compat-data#10414
sideshowbarker
added a commit
to w3c/browser-compat-data
that referenced
this pull request
May 10, 2021
httpwg/http-extensions#878 removed the Accept-CH-Lifetime HTTP header from the Client Hints spec, and it’s not part of any other spec — so this change marks it deprecated and standard_track:false. Related MDN change: mdn/content#4854
mirunacurtean
pushed a commit
to mdn/content
that referenced
this pull request
May 10, 2021
httpwg/http-extensions#878 removed the Accept-CH-Lifetime HTTP header from the Client Hints spec, and it’s not part of any other spec — so this change adds Deprecated and Non-standard headers to the Accept-CH-Lifetime article. Related BCD change: mdn/browser-compat-data#10414
Elchi3
pushed a commit
to mdn/browser-compat-data
that referenced
this pull request
May 10, 2021
httpwg/http-extensions#878 removed the Accept-CH-Lifetime HTTP header from the Client Hints spec, and it’s not part of any other spec — so this change marks it deprecated and standard_track:false. Related MDN change: mdn/content#4854
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on discussion at IETF 105, removing explicit lifetime in favor of
implicit opt-in registration and persistence.
@martinthomson can you please take a look? In particular, current language states the preference should be persisted but doesn't explicitly state for what the lifetime is.. Modulo, in privacy section we do talk about MUST criteria for clearing it. Any suggestions or recommendations for how to best approach this?