diff --git a/fetch.bs b/fetch.bs index 70f08d11c..b023ee89c 100644 --- a/fetch.bs +++ b/fetch.bs @@ -53,14 +53,6 @@ url:https://tools.ietf.org/html/rfc7234#section-1.2.1;text:delta-seconds;type:df "WSP": { "aliasOf": "RFC6455" }, - "CLIENT-HINTS": { - "authors": [ - "Ilya Grigorik" - ], - "href": "https://tools.ietf.org/html/draft-ietf-httpbis-client-hints", - "publisher": "IETF", - "title": "HTTP Client Hints" - }, "HTTPVERBSEC1": { "publisher": "US-CERT", "href": "https://www.kb.cert.org/vuls/id/867593", @@ -697,14 +689,6 @@ fetch("https://victim.example/naïve-endpoint", { -
`DPR` -
`Downlink` -
`Save-Data` -
`Viewport-Width` -
`Width` -

If value, once extracted, is failure, then - return false. -

Otherwise

Return false. @@ -1311,16 +1295,6 @@ to not have to set request's referrer.

This can be used to override a referrer policy associated with an environment settings object. - -

A request has an associated -client hints list, -which is a client-hints list. Unless stated -otherwise, it is the empty list. - -

This will be used to override a client hints list associated with -an environment settings object. -[[!CLIENT-HINTS]] -

A request has an associated synchronous flag. Unless stated otherwise it is unset. @@ -2141,19 +2115,6 @@ run these steps: -

Client hints list

- -

This section will be integrated into HTTP Client Hints. -[[!CLIENT-HINTS]] - - -

A client hints list is a -list of -Client hint tokens, each -of which is one of `DPR`, `Save-Data`, `Viewport-Width`, or -`Width`. - -

Streams

This section might be integrated into other standards, such as IDL. @@ -3145,57 +3106,10 @@ the request. for HTTP/2, and equivalent information used to prioritize dispatch and processing of HTTP/1 fetches. -

  • -

    If request is a navigation request, a user agent should, for each - header name (hintName) in the first column of the - following table, if request's header list - does not contain hintName, then - append - hintName/the value given in the same row on the second column, to - request's header list. - - - - - - -
    Name - Value -
    `DPR` - a suitable dpr value -
    `Save-Data` - a suitable save-data value -
    `Viewport-Width` - a suitable viewport-width value -
    -

  • If request is a subresource request, then:

      -
    1. -

      For each hintName of request's - client hints list: - -

        -
      1. -

        Let value be the first matching statement, switching on hintName: - -

        -
        `DPR` -
        a suitable dpr value -
        `Save-Data` -
        a suitable save-data value -
        `Viewport-Width` -
        a suitable viewport-width value -
        `Width` -
        a suitable width value -
        - -
      2. A user agent should append - hintName/value to request's header list. -

      -
    2. Let record be a new fetch record consisting of request and this instance of the