- From: Mike West <notifications@github.com>
- Date: Thu, 24 May 2018 06:42:59 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/733/review/122997462@github.com>
mikewest commented on this pull request.
> +
+ <li>
+ <p>If <var>request</var>'s <a for=request>origin</a> is <a>same origin</a> with
+ <var>request</var>'s <a for=request>current url</a>'s <a for=url>origin</a>, then return
+ <b>allowed</b>.
+
+ <p class=note>A cross-origin response redirecting to a same or same-site resource with the
+ `<a http-header><code>Cross-Origin-Resource-Policy</code></a>` header specified does not affect
+ anything.
+ <!-- We could make this have an effect if we fix https://github.com/whatwg/fetch/pull/594 first,
+ but even then we normally do not let this have any effect for "no-cors" so it would be
+ somewhat inconsistent if it did here, but might still be better... -->
+
+ <li><p>Let <var>policy</var> be the <a>combined value</a> with
+ `<a http-header><code>Cross-Origin-Resource-Policy</code></a>` and <var>response</var>'s
+ <a for=response>header list</a>.
I don't think there's any requirement that all the items in a list are the same type. @mnot can confirm, but my understanding is that we could have `same` and `same-site` as "labels" and some other type ("string", I suppose) for origins.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/733#discussion_r190590246
Received on Thursday, 24 May 2018 13:43:24 UTC