Re: [ResourceTiming] "timing allow check" steps depend on underdefined behavior from Boris Zbarsky on 2014-05-22 (public-web-perf@w3.org from May 2014)

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 22 May 2014 12:42:30 -0400
To: Jatinder Mann <jmann@microsoft.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <537E28F6.6080608@mit.edu>

On 5/22/14, 12:15 PM, Jatinder Mann wrote:
> Good point, not all cross-origin fetches will have an Origin header. What if we simplified step 3 of the algorithm as so:
>
> 3.     If the value of Timing-Allow-Origin is not a match for the value of the origin of the current document

What does "current document" mean?

-Boris

Received on Thursday, 22 May 2014 16:42:58 UTC