Block redirects to non-HTTP schemes #309
Comments
|
I think I'll fix this with the caveat that we might need to rearchitect a bit more based on further navigate findings. |
annevk
added a commit
to web-platform-tests/wpt
that referenced
this issue
May 30, 2016
See whatwg/fetch#309 for context.
annevk
added a commit
to web-platform-tests/wpt
that referenced
this issue
May 30, 2016
See whatwg/fetch#309 for context.
arronei
pushed a commit
to arronei/web-platform-tests
that referenced
this issue
Jun 14, 2016
See whatwg/fetch#309 for context.
ivanzr
pushed a commit
to ivanzr/web-platform-tests
that referenced
this issue
Jun 29, 2016
See whatwg/fetch#309 for context.
This was referenced Sep 30, 2016
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note that HTML's navigate is probably a special case still with its manual redirect logic (see whatwg/html#461) although Firefox appears quite strict there as well (not supporting mailto or facetime URLs, which appear to work in other browsers).
(One difference I've found is that Firefox supports data URLs in
Locationheaders when navigating, but not otherwise. That is also the case for Safari. Chrome never supports data URLs.)The text was updated successfully, but these errors were encountered: