W3C home > Mailing lists > Public > public-tracking@w3.org > April 2017

issue 23 (Server Push)

From: Mike O'Neill <michael.oneill@baycloud.com>
Date: Sat, 1 Apr 2017 12:33:01 +0100
To: <public-tracking@w3.org>
Message-ID: <039501d2aadb$b8a904d0$29fb0e70$@baycloud.com>
The text for Server Push was wrong, it was referring to a paragraph in the
Origin Policy spec where I had copied it. It should have been as follows:

To ensure that user agents always have the most recent Tracking Status
Resource in their cache, servers SHOULD use the Server Push mechanism
defined in [RFC7540] whenever a state-changing request may have changed it.

Send a PUSH_PROMISE frame with a minimal request for the resource at
/.well-known/dnt/{status-id} with the "Cookie" and "DNT" headers set as they
were in the initiating state-changing request, and the status-id value the
value as returned in the Tk field-value response to that request.
Begin delivering the response to the PUSH_PROMISE request.
Received on Saturday, 1 April 2017 11:34:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:40:34 UTC