- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Sun, 18 May 2014 15:00:37 +0200
- To: Arvind Jain <arvind@google.com>
- Cc: Jonas Sicking <jonas@sicking.cc>, Jatinder Mann <jmann@microsoft.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>, Mike West <mkwst@google.com>
(Mike, see end.) On Sat, May 17, 2014 at 11:32 PM, Arvind Jain <arvind@google.com> wrote: > Hi Anne, > The latest draft is at > https://w3c.github.io/web-performance/specs/Beacon/Overview.html > (as per my last mail). Could you have the other draft link to this one or at least clearly mark it obsolete? > I removed the duplicate text you cite in your comment (1) below. "User agents MUST honor the HTTP headers (including, in particular, redirects and HTTP cookie headers), but MUST ignore any entity bodies returned in the response" is still there. > Re. (3), the url parser is used but via the "Resolve-a-url" section. Because? Also, you did not answer my question about further restricting this to http/https. > Re. (2), I have not made a change. Because? > Could you please take another look? Is it okay if the Beacon-Age header can be set by XMLHttpRequest? Should it become a restricted header? What about CSP? Should we introduce a "ping" request context for <a ping> and sendBeacon()? And a ping-src directive or some such maybe. (Any reason it's sendBeacon() and not sendPing()?) -- http://annevankesteren.nl/
Received on Sunday, 18 May 2014 13:01:04 UTC