A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "URL"

From WHATWG Wiki
Jump to: navigation, search
(Schemes)
(Implementations)
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{CC0 page}}
 +
 
This documents research and notes around URLs for the [http://url.spec.whatwg.org/ URL standard].
 
This documents research and notes around URLs for the [http://url.spec.whatwg.org/ URL standard].
  
Line 10: Line 12:
 
* http://mxr.mozilla.org/mozilla-central/source/dom/src/jsurl/nsJSProtocolHandler.cpp (javascript URLs)
 
* http://mxr.mozilla.org/mozilla-central/source/dom/src/jsurl/nsJSProtocolHandler.cpp (javascript URLs)
 
* http://mxr.mozilla.org/mozilla-central/source/nsprpub/pr/src/misc/prnetdb.c#1544 (IPv6)
 
* http://mxr.mozilla.org/mozilla-central/source/nsprpub/pr/src/misc/prnetdb.c#1544 (IPv6)
 +
* https://code.google.com/p/chromium/codesearch
  
 
==Tests==
 
==Tests==
Line 47: Line 50:
 
==Schemes==
 
==Schemes==
  
Post-processing of parsed URLs that represent a resource:
+
Apart from the scheme-types listed below, the URL Standard identifies "relative schemes", used for parsing a URL into a parsed URL.
 +
 
 +
=== Purpose-specific schemes ===
 +
 
 +
URL schemes are purpose-specific schemes if they only work in one context. These only work for WebSocket:
 +
 
 +
* ws
 +
* wss
 +
 
 +
=== Fetch schemes ===
 +
 
 +
URL schemes are resource schemes if fetching the URL results in either a network error or a resource with associated MIME type (potentially sniffed).
  
 
; ftp
 
; ftp
; gopher
 
 
; http
 
; http
; https
+
; https : These all can be used by the corresponding protocol directly.
; ws
 
; wss : These all can be used by the corresponding protocol directly.
 
 
; file : Needs platform-specific interpretation and mapping to a resource on a the local file system.
 
; file : Needs platform-specific interpretation and mapping to a resource on a the local file system.
 
; data : Needs its resource and MIME type information retrieved from its scheme data/query.
 
; data : Needs its resource and MIME type information retrieved from its scheme data/query.
; javascript : Needs its resource retrieved from its scheme data/query/fragment.
+
; blob
 
; about : The resource is effectively the result of passing scheme data to a hash table (not sure if case-sensitive or not; definitely no percent decoding). Query and fragment can be used by the resource.
 
; about : The resource is effectively the result of passing scheme data to a hash table (not sure if case-sensitive or not; definitely no percent decoding). Query and fragment can be used by the resource.
  
Post-processing of parsed URLs that do not represent a resource (handled outside the fetching context, typically in a separate application):
+
(The same-origin definition should maybe account for about/blob/data.)
  
; irc : If we change irc to a relative scheme could it be used by the IRC protocol directly?
+
=== Navigate schemes ===
; aim
+
 
; xmpp
+
* The "fetch schemes" -> use "fetch"
; ymsgr
+
* javascript
; msnim
+
* Not the "purpose-specific schemes" -> error
; skype
+
* All other schemes (including "external schemes")
; callto
+
 
; tel
+
=== External schemes ===
; fax
+
 
; mailto : Require processing of scheme data/query. Do not use fragment?
+
Depending on the context, schemes not listed above will either launch an external application or result in a network error. Examples:
 +
 
 +
* mailto
 +
* skype
  
 
==IDNA==
 
==IDNA==
  
Definitions:
+
=== Definitions ===
  
 
* IDNA2003+: IDNA2003 with Unicode updated to the latest version. (So not NFKC from Unicode 3.2., although [http://docs.python.org/2/library/unicodedata.html#unicodedata.ucd_3_2_0 Python might do that]... ) Restrictions on display might be in place.
 
* IDNA2003+: IDNA2003 with Unicode updated to the latest version. (So not NFKC from Unicode 3.2., although [http://docs.python.org/2/library/unicodedata.html#unicodedata.ucd_3_2_0 Python might do that]... ) Restrictions on display might be in place.
 
* IDNA2008+: IDNA2008 with [http://tools.ietf.org/html/rfc5895#section-2 RFC 5895 section 2] mapping and IDNA2003 domain label separators. Display is restricted to IDNA2008, lookup is unrestricted (everything gets Punycoded).
 
* IDNA2008+: IDNA2008 with [http://tools.ietf.org/html/rfc5895#section-2 RFC 5895 section 2] mapping and IDNA2003 domain label separators. Display is restricted to IDNA2008, lookup is unrestricted (everything gets Punycoded).
  
Implementations:
+
=== Implementations ===
  
* IDNA2003+: Safari, Chrome, Firefox, Internet Explorer
+
* IDNA2003+: Safari, Chrome, Firefox
* IDNA2008+: Opera
+
** Changing, see e.g. https://codereview.chromium.org/23642003#msg4
 +
* IDNA2008+: Internet Explorer?
  
Tests:
+
=== Tests ===
  
 
* http://mathias.html5.org/tests/url/idna2003-separators/ IDNA2003 domain label separators are supported everywhere
 
* http://mathias.html5.org/tests/url/idna2003-separators/ IDNA2003 domain label separators are supported everywhere
  
Required algorithms:
+
=== Algorithms ===
  
 
* ToLabels(domain string) -> ASCII-label list (empty label at the end signifies trailing dot) or failure.  
 
* ToLabels(domain string) -> ASCII-label list (empty label at the end signifies trailing dot) or failure.  
Line 97: Line 112:
 
(For convenience maybe ToASCII and ToUnicode should accept lists too.)
 
(For convenience maybe ToASCII and ToUnicode should accept lists too.)
  
Notes:
+
=== UI ===
 +
 
 +
Note that this has potential security implications too, but does not matter for interoperability.
 +
 
 +
* http://www.chromium.org/developers/design-documents/idn-in-google-chrome (also includes summary for other browsers)
 +
* https://wiki.mozilla.org/IDN_Display_Algorithm
 +
* http://www.alvestrand.no/pipermail/idna-update/2011-December/date.html (has lots of background discussion)
 +
* https://bugs.webkit.org/show_bug.cgi?id=126627
 +
 
 +
=== Notes ===
  
 
* Input to DNS is a byte array. (This means that "_" and byte 0x03 can be valid input. Not sure whether "." works within a label. Higher than 0x7F cannot happen if IDNA is used.)
 
* Input to DNS is a byte array. (This means that "_" and byte 0x03 can be valid input. Not sure whether "." works within a label. Higher than 0x7F cannot happen if IDNA is used.)
Line 105: Line 129:
  
 
[[Category:Spec coordination]]
 
[[Category:Spec coordination]]
 +
 +
== Requests and Issues ==
 +
=== How to compare URLs ===
 +
There is at least one specification (being implemented) that needs a reference for how to compare URLs for equivalency.
 +
* http://microformats.org/wiki/representative-hcard-parsing
 +
 +
Hence, request:
 +
 +
New section/feature in the URL spec:
 +
 +
"How to compare URLs"
 +
 +
with something like: "parse them first and then compare the serialization"
 +
 +
See: http://krijnhoetmer.nl/irc-logs/whatwg/20141006#l-843
 +
for background / discussion.

Latest revision as of 15:31, 20 June 2015

The contents of this page, URL, and all edits made to this page in its history, are hereby released under the CC0 Public Domain Dedication, as described in WHATWG Wiki:Copyrights.

This documents research and notes around URLs for the URL standard.

Implementations

Tests

Variants of the following code (runs in Live DOM Viewer) are useful to test which code points are URL escaped in browsers:

<!DOCTYPE html>
<script>
var a = document.createElement("a")

i = 0
cp = 0x100

while ( i < cp ) {
  a.href = "http://x" + String.fromCharCode(i) + "@x/"
  if(a.href.length != "http://x)@x/".length) {
    w(a.href)
  }
  i++
}
</script>

Parsing

JavaScript libraries

For improving the API we might want to take inspiration from:

Schemes

Apart from the scheme-types listed below, the URL Standard identifies "relative schemes", used for parsing a URL into a parsed URL.

Purpose-specific schemes

URL schemes are purpose-specific schemes if they only work in one context. These only work for WebSocket:

  • ws
  • wss

Fetch schemes

URL schemes are resource schemes if fetching the URL results in either a network error or a resource with associated MIME type (potentially sniffed).

ftp
http
https 
These all can be used by the corresponding protocol directly.
file 
Needs platform-specific interpretation and mapping to a resource on a the local file system.
data 
Needs its resource and MIME type information retrieved from its scheme data/query.
blob
about 
The resource is effectively the result of passing scheme data to a hash table (not sure if case-sensitive or not; definitely no percent decoding). Query and fragment can be used by the resource.

(The same-origin definition should maybe account for about/blob/data.)

Navigate schemes

  • The "fetch schemes" -> use "fetch"
  • javascript
  • Not the "purpose-specific schemes" -> error
  • All other schemes (including "external schemes")

External schemes

Depending on the context, schemes not listed above will either launch an external application or result in a network error. Examples:

  • mailto
  • skype

IDNA

Definitions

  • IDNA2003+: IDNA2003 with Unicode updated to the latest version. (So not NFKC from Unicode 3.2., although Python might do that... ) Restrictions on display might be in place.
  • IDNA2008+: IDNA2008 with RFC 5895 section 2 mapping and IDNA2003 domain label separators. Display is restricted to IDNA2008, lookup is unrestricted (everything gets Punycoded).

Implementations

Tests

Algorithms

  • ToLabels(domain string) -> ASCII-label list (empty label at the end signifies trailing dot) or failure.
  • ToASCII(Unicode-label) -> ASCII-label.
  • ToUnicode(ASCII-label) -> Unicode label.

(For convenience maybe ToASCII and ToUnicode should accept lists too.)

UI

Note that this has potential security implications too, but does not matter for interoperability.

Notes

Requests and Issues

How to compare URLs

There is at least one specification (being implemented) that needs a reference for how to compare URLs for equivalency.

Hence, request:

New section/feature in the URL spec:

"How to compare URLs"

with something like: "parse them first and then compare the serialization"

See: http://krijnhoetmer.nl/irc-logs/whatwg/20141006#l-843 for background / discussion.