From d89d1e73601edf7f31a590f549b722ad1f910dbf Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Thu, 9 Jun 2016 11:22:48 +0200 Subject: [PATCH] Expose fragments of request URLs Fixes #214. Though only for request URLs as exposing the fragment on a response is not an accurate representation of what happens. --- Overview.html | 47 +++++++++++++++++++++++------------------------ Overview.src.html | 47 +++++++++++++++++++++++------------------------ 2 files changed, 46 insertions(+), 48 deletions(-) diff --git a/Overview.html b/Overview.html index f8dc70b14..f5a11e353 100644 --- a/Overview.html +++ b/Overview.html @@ -219,11 +219,11 @@

3 Infrastructure


-

A fetch URL is a URL for -which implementations need not store the -fragment as it is never -exposed. When serialized, -the exclude fragment flag is set, meaning implementations can store the +

A response URL is a +URL for which implementations need not store the +fragment as it is never exposed. When +serialized, the +exclude fragment flag is set, meaning implementations can store the fragment nonetheless.


@@ -678,12 +678,13 @@

3.1.5 Requests

described in HTTP fetch.

A request has an associated -url (a fetch URL). +url (a +URL).

Implementations are encouraged to make this a pointer to the first -fetch URL in request's -url list. It is provided as a distinct field solely for -the convenience of other standards hooking into Fetch. +URL in +request's url list. +It is provided as a distinct field solely for the convenience of other standards hooking into Fetch.

A request has an associated local-URLs-only flag. Unless stated otherwise it is unset. @@ -1087,14 +1088,14 @@

3.1.5 Requests

A request has an associated url list (a list of one or more -fetch URLs). Unless stated otherwise, it is a list +URLs). Unless stated otherwise, it is a list containing a copy of request's url.

A request has an associated current url. It is a pointer to the last -fetch URL in request's -url list. +URL in +request's url list.

A request has an associated redirect count. Unless stated otherwise, @@ -1178,20 +1179,18 @@

3.1.6 Responses

end-user abort, fatal, or timeout.

A response has an associated -url. It is a pointer to the last -fetch URL in response's -url list and null if -response's +url. It is a pointer to the last response URL in +response's url list +and null if response's url list is the empty list.

A response has an associated url list (a list of zero or more -fetch URLs). Unless stated otherwise, it is the empty list. +response URLs). Unless stated otherwise, it is the empty list. -

Except for the last fetch URL, if any, a -response's -url list cannot be exposed to script. That -would violate atomic HTTP redirect handling. +

Except for the last response URL, if any, a +response's url list +cannot be exposed to script. That would violate atomic HTTP redirect handling.

A response has an associated status, which is a status. Unless stated @@ -3806,7 +3805,8 @@

5.8 CORS-preflight cach