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 Chat (such as one of these permanent autoconfirmed members).

URL: Difference between revisions

From WHATWG Wiki
Jump to navigation Jump to search
(→‎Schemes: add blob)
Line 58: Line 58:
; 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.
; 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.


Revision as of 19:57, 24 November 2012

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

Post-processing of parsed URLs that represent a resource:

ftp
gopher
http
https
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.
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.

Post-processing of parsed URLs that do not represent a resource (handled outside the fetching context, typically in a separate application):

irc
If we change irc to a relative scheme could it be used by the IRC protocol directly?
aim
xmpp
ymsgr
msnim
skype
callto
tel
fax
mailto
Require processing of scheme data/query. Do not use fragment?

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:

  • IDNA2003+: Safari, Chrome, Firefox, Internet Explorer
  • IDNA2008+: Opera

Tests:

Required 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.)

Notes:

Retrieved from "https://wiki.whatwg.org/index.php?title=URL&oldid=8804"