From ff50b829504738af5cf797e4e74a8c55744e588e Mon Sep 17 00:00:00 2001 From: Ilya Grigorik Date: Wed, 25 May 2016 15:41:26 -0700 Subject: [PATCH] make Save-Data extensible - only one "on" token value is recognized today - allow extension values (none defined) Discussion: https://github.com/httpwg/http-extensions/issues/168 --- draft-ietf-httpbis-client-hints.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/draft-ietf-httpbis-client-hints.md b/draft-ietf-httpbis-client-hints.md index 8244542ca..257c22bf7 100644 --- a/draft-ietf-httpbis-client-hints.md +++ b/draft-ietf-httpbis-client-hints.md @@ -65,7 +65,7 @@ normative: ins: H. W. Lie seriesinfo: "W3C Recommendation": REC-CSS2-20110607 - + informative: RFC6265: @@ -247,10 +247,11 @@ If Downlink occurs in a message more than once, the minimum value should be used The "Save-Data" request header field is a token that indicates client's preference for reduced data usage, due to high transfer costs, slow connection speeds, or other reasons. ~~~ abnf7230 - Save-Data = "on" + Save-Data : sd-token *( ";" [sd-token] ) + sd-token = token ~~~ -The token is a signal indicating explicit user opt-in into a reduced data usage mode on the client, and when communicated to origins allows them to deliver alternate content honoring such preference - e.g. smaller image and video resources, alternate markup, and so on. +This document defines the "on" sd-token value, which is used as a signal indicating explicit user opt-in into a reduced data usage mode on the client, and when communicated to origins allows them to deliver alternate content honoring such preference - e.g. smaller image and video resources, alternate markup, and so on. New token and extension token values can only be defined by revisions of this specification. # Examples