WHATWG Wiki - User contributions [en]

Band names

2014-09-24T21:01:52Z

SimonSapin: /* Album titles */

These are band names collected from #whatwg.

* Bogus DOM
* The Unpaired Surrogates
* Lone Surrogates
* The Designated Experts
* Spidermonkey and the GC Jitters
* Polyglot Heartbeat
* Extant Web Corpus
* Ambushed by Ambiguity
* Ambiguous Ampersands
* bad value robot
* Abort These Steps

== Album titles ==

* User Bang Important Rule
* Polygoat

URL schemes

2012-12-02T09:58:20Z

SimonSapin: /* data: URLs */ Moved to GitHub.

URL schemes

2012-12-01T21:20:08Z

SimonSapin: /* data: URLs */ Add a TODO for missing parsing steps

Licensing: this page is under CC0, not the MIT License.

== about: URLs ==

'''about: URLs''' serve as identifier, potentially with an associated resource. The identifier is given in the URL's scheme data.

{| class="wikitable"
|-
! Identifier
! Resource
! Notes
|-
| "blank"
| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
|
|-
| "invalid"
| -
| Used to represent a network error. See also [http://dev.w3.org/csswg/css3-values/ CSS Values and Units].
|-
| "legacy-compat"
| -
| Used in HTML for XSLT serializers.
|-
| "srcdoc"
| -
| Used in HTML for its <iframe srcdoc> feature.
|-
| "unicorn"
| A resource whose Content-Type is image/svg+xml and entity body is the contents of [http://html5.org/temp/unicorn.svg unicorn.svg].
| Unicorn!
|}

To '''obtain a resource''' from an about: URL, run these steps:

* If URL's scheme data is not the literal string "blank" or "unicorn", return a network error. (URL's query and URL's fragment are simply not taken into account and can be anything.)
* Return the resource corresponding to the identifier as listed in the table above, with HTTP status code 200 and HTTP status text "OK".

See also [http://tools.ietf.org/html/rfc6694 The "about" URI Scheme] and [http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xml "about" URI Tokens] which this wiki page obsoletes.

=== Examples ===

{| class="wikitable"
|-
! Input
! Result
|-
| about:blanK
| network error (uppercase K)
|-
| about:bl%61nk
| network error (no percent decoding by either the URL parser or the obtain a resource algorithm)
|-
| about:blank?teehee
| works (query does not matter)
|-
| about:blank?teehee#hihi
| works (fragment does not matter either)
|}

== javascript: URLs ==

'''javascript: URLs''' represent a JavaScript script.

To '''obtain a script''' from a javascript: URL, run these steps:

* Let ''input'' be the concatenation of URL's scheme data, followed by "?" and URL's query if URL's query is non-null, followed by "#" and URL's fragment if URL's fragment is non-null.
* Set ''input'' to the result of [http://url.spec.whatwg.org/#percent-decode percent decoding] ''input''.
* If ''input'' starts with a U+FEFF, remove a single occurrence from the start of ''input''.
* Return ''input''.

See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which this wiki page obsoletes.

== data: URLs ==

See [https://www.w3.org/Bugs/Public/show_bug.cgi?id=19494 Bug 19494] and other stuff linked from there. This is a more precise definition for [http://tools.ietf.org/html/rfc2397 RFC2397]

To '''obtain a resource''' from a [http://url.spec.whatwg.org/#concept-parsed-url parsed URL] whose ''scheme'' is a ASCII case-insensitive match for "data:", run these steps:

* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].
* If the URL’s [http://url.spec.whatwg.org/#concept-url-query query] is not null, append "?" and the query to ''input''.
* If ''input'' does not contain a U+002C COMMA code point, return a network error and abort these steps. (Note: the comma can come either from the scheme data or the query.)
* Split ''input'' at the first comma. Set ''header'' and ''body'' to the parts before and after the comma, respectively. ('''Issue:''' what if the comma is an a MIME quoted string for a parameter value? Example: <code>data:text/plain;foo="bar,baz";charset=utf8,body</code>)
* Set ''body-bytes'' to the result of running ''percent decode to bytes'' on ''body''.
* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
** Remove the matched substring from ''header''
** Decode ''body-bytes'' with the [https://tools.ietf.org/html/rfc4648#section-4 Base 64 Encoding]. ('''Issues:''' Return an error on "invalid" base64? What is invalid? Also accept the ''URL and Filename Safe Alphabet''? Mixed alphabets in the same body? Ignore which non-alphabet bytes? Missing/too little/too much padding?)
* Return a response with ''header'' as a ''Content-Type'' header and ''body-bytes'' as the body. The parsing and interpretation of ''header'' must be the same as for an HTTP ''Content-Type'' header. ('''Issue:''' what can we reference to define that?)

'''TODO:''' The algorithm is missing this part of RFC2397:
<blockquote>If <mediatype> is omitted, it
defaults to text/plain;charset=US-ASCII. As a shorthand,
"text/plain" can be omitted but the charset parameter supplied.</blockquote>

'''Note:''' this definition does not impose any length limit on data: URLs. When doing [http://url.spec.whatwg.org/#concept-url-parser URL parsing] followed by this algorithm, implementation are allowed to skip some intermediate steps in order to process large URLs efficiently, as long as the "black box" behavior the same.

To '''percent decode to bytes''', run the same algorithm as '''[http://url.spec.whatwg.org/#percent-decode percent decode]''' but replacing the last step with "Return ''bytes''."

== Others ==

* [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol ws: & wss:]
* See [http://en.wikipedia.org/wiki/URI_scheme Wikipedia]
* See [http://www.iana.org/assignments/uri-schemes.html IANA]

[[Category:Registries]]
[[Category:Spec coordination]]

URL schemes

2012-11-30T17:13:58Z

SimonSapin: /* data: URLs */ Allow (and suggest) some optimization.

Licensing: this page is under CC0, not the MIT License.

== about: URLs ==

'''about: URLs''' serve as identifier, potentially with an associated resource. The identifier is given in the URL's scheme data.

{| class="wikitable"
|-
! Identifier
! Resource
! Notes
|-
| "blank"
| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
|
|-
| "invalid"
| -
| Used to represent a network error. See also [http://dev.w3.org/csswg/css3-values/ CSS Values and Units].
|-
| "legacy-compat"
| -
| Used in HTML for XSLT serializers.
|-
| "srcdoc"
| -
| Used in HTML for its <iframe srcdoc> feature.
|-
| "unicorn"
| A resource whose Content-Type is image/svg+xml and entity body is the contents of [http://html5.org/temp/unicorn.svg unicorn.svg].
| Unicorn!
|}

To '''obtain a resource''' from an about: URL, run these steps:

* If URL's scheme data is not the literal string "blank" or "unicorn", return a network error. (URL's query and URL's fragment are simply not taken into account and can be anything.)
* Return the resource corresponding to the identifier as listed in the table above, with HTTP status code 200 and HTTP status text "OK".

See also [http://tools.ietf.org/html/rfc6694 The "about" URI Scheme] and [http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xml "about" URI Tokens] which this wiki page obsoletes.

=== Examples ===

{| class="wikitable"
|-
! Input
! Result
|-
| about:blanK
| network error (uppercase K)
|-
| about:bl%61nk
| network error (no percent decoding by either the URL parser or the obtain a resource algorithm)
|-
| about:blank?teehee
| works (query does not matter)
|-
| about:blank?teehee#hihi
| works (fragment does not matter either)
|}

== javascript: URLs ==

'''javascript: URLs''' represent a JavaScript script.

To '''obtain a script''' from a javascript: URL, run these steps:

* Let ''input'' be the concatenation of URL's scheme data, followed by "?" and URL's query if URL's query is non-null, followed by "#" and URL's fragment if URL's fragment is non-null.
* Set ''input'' to the result of [http://url.spec.whatwg.org/#percent-decode percent decoding] ''input''.
* If ''input'' starts with a U+FEFF, remove a single occurrence from the start of ''input''.
* Return ''input''.

See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which this wiki page obsoletes.

== data: URLs ==

See [https://www.w3.org/Bugs/Public/show_bug.cgi?id=19494 Bug 19494] and other stuff linked from there.

To '''obtain a resource''' from a [http://url.spec.whatwg.org/#concept-parsed-url parsed URL] whose ''scheme'' is a ASCII case-insensitive match for "data:", run these steps:

* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].
* If the URL’s [http://url.spec.whatwg.org/#concept-url-query query] is not null, append "?" and the query to ''input''.
* If ''input'' does not contain a U+002C COMMA code point, return a network error and abort these steps. (Note: the comma can come either from the scheme data or the query.)
* Split ''input'' at the first comma. Set ''header'' and ''body'' to the parts before and after the comma, respectively. ('''Issue:''' what if the comma is an a MIME quoted string for a parameter value? Example: <code>data:text/plain;foo="bar,baz";charset=utf8,body</code>)
* Set ''body-bytes'' to the result of running ''percent decode to bytes'' on ''body''.
* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
** Remove the matched substring from ''header''
** Decode ''body-bytes'' with the [https://tools.ietf.org/html/rfc4648#section-4 Base 64 Encoding]. ('''Issues:''' Return an error on "invalid" base64? What is invalid? Also accept the ''URL and Filename Safe Alphabet''? Mixed alphabets in the same body? Ignore which non-alphabet bytes? Missing/too little/too much padding?)
* Return a response with ''header'' as a ''Content-Type'' header and ''body-bytes'' as the body. The parsing and interpretation of ''header'' must be the same as for an HTTP ''Content-Type'' header. ('''Issue:''' what can we reference to define that?)

'''Note:''' this definition does not impose any length limit on data: URLs. When doing [http://url.spec.whatwg.org/#concept-url-parser URL parsing] followed by this algorithm, implementation are allowed to skip some intermediate steps in order to process large URLs efficiently, as long as the "black box" behavior the same.

To '''percent decode to bytes''', run the same algorithm as '''[http://url.spec.whatwg.org/#percent-decode percent decode]''' but replacing the last step with "Return ''bytes''."

== Others ==

* [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol ws: & wss:]
* See [http://en.wikipedia.org/wiki/URI_scheme Wikipedia]
* See [http://www.iana.org/assignments/uri-schemes.html IANA]

[[Category:Registries]]
[[Category:Spec coordination]]

URL schemes

2012-11-30T17:01:47Z

SimonSapin: /* data: URLs */ issue: what to reference for parsing a Content-Type header?

Licensing: this page is under CC0, not the MIT License.

== about: URLs ==

'''about: URLs''' serve as identifier, potentially with an associated resource. The identifier is given in the URL's scheme data.

{| class="wikitable"
|-
! Identifier
! Resource
! Notes
|-
| "blank"
| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
|
|-
| "invalid"
| -
| Used to represent a network error. See also [http://dev.w3.org/csswg/css3-values/ CSS Values and Units].
|-
| "legacy-compat"
| -
| Used in HTML for XSLT serializers.
|-
| "srcdoc"
| -
| Used in HTML for its <iframe srcdoc> feature.
|-
| "unicorn"
| A resource whose Content-Type is image/svg+xml and entity body is the contents of [http://html5.org/temp/unicorn.svg unicorn.svg].
| Unicorn!
|}

To '''obtain a resource''' from an about: URL, run these steps:

* If URL's scheme data is not the literal string "blank" or "unicorn", return a network error. (URL's query and URL's fragment are simply not taken into account and can be anything.)
* Return the resource corresponding to the identifier as listed in the table above, with HTTP status code 200 and HTTP status text "OK".

See also [http://tools.ietf.org/html/rfc6694 The "about" URI Scheme] and [http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xml "about" URI Tokens] which this wiki page obsoletes.

=== Examples ===

{| class="wikitable"
|-
! Input
! Result
|-
| about:blanK
| network error (uppercase K)
|-
| about:bl%61nk
| network error (no percent decoding by either the URL parser or the obtain a resource algorithm)
|-
| about:blank?teehee
| works (query does not matter)
|-
| about:blank?teehee#hihi
| works (fragment does not matter either)
|}

== javascript: URLs ==

'''javascript: URLs''' represent a JavaScript script.

To '''obtain a script''' from a javascript: URL, run these steps:

* Let ''input'' be the concatenation of URL's scheme data, followed by "?" and URL's query if URL's query is non-null, followed by "#" and URL's fragment if URL's fragment is non-null.
* Set ''input'' to the result of [http://url.spec.whatwg.org/#percent-decode percent decoding] ''input''.
* If ''input'' starts with a U+FEFF, remove a single occurrence from the start of ''input''.
* Return ''input''.

See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which this wiki page obsoletes.

== data: URLs ==

See [https://www.w3.org/Bugs/Public/show_bug.cgi?id=19494 Bug 19494] and other stuff linked from there.

To '''obtain a resource''' from a [http://url.spec.whatwg.org/#concept-parsed-url parsed URL] whose ''scheme'' is a ASCII case-insensitive match for "data:", run these steps:

* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].
* If the URL’s [http://url.spec.whatwg.org/#concept-url-query query] is not null, append "?" and the query to ''input''.
* If ''input'' does not contain a U+002C COMMA code point, return a network error and abort these steps. (Note: the comma can come either from the scheme data or the query.)
* Split ''input'' at the first comma. Set ''header'' and ''body'' to the parts before and after the comma, respectively. ('''Issue:''' what if the comma is an a MIME quoted string for a parameter value? Example: <code>data:text/plain;foo="bar,baz";charset=utf8,body</code>)
* Set ''body-bytes'' to the result of running ''percent decode to bytes'' on ''body''.
* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
** Remove the matched substring from ''header''
** Decode ''body-bytes'' with the [https://tools.ietf.org/html/rfc4648#section-4 Base 64 Encoding]. ('''Issues:''' Return an error on "invalid" base64? What is invalid? Also accept the ''URL and Filename Safe Alphabet''? Mixed alphabets in the same body? Ignore which non-alphabet bytes? Missing/too little/too much padding?)
* Return a response with ''header'' as a ''Content-Type'' header and ''body-bytes'' as the body. The parsing and interpretation of ''header'' must be the same as for an HTTP ''Content-Type'' header. ('''Issue:''' what can we reference to define that?)

To '''percent decode to bytes''', run the same algorithm as '''[http://url.spec.whatwg.org/#percent-decode percent decode]''' but replacing the last step with "Return ''bytes''."

== Others ==

* [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol ws: & wss:]
* See [http://en.wikipedia.org/wiki/URI_scheme Wikipedia]
* See [http://www.iana.org/assignments/uri-schemes.html IANA]

[[Category:Registries]]
[[Category:Spec coordination]]

URL schemes

2012-11-30T16:55:18Z

SimonSapin: /* data: URLs */ Expand on errors and invalid base64

Licensing: this page is under CC0, not the MIT License.

== about: URLs ==

'''about: URLs''' serve as identifier, potentially with an associated resource. The identifier is given in the URL's scheme data.

{| class="wikitable"
|-
! Identifier
! Resource
! Notes
|-
| "blank"
| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
|
|-
| "invalid"
| -
| Used to represent a network error. See also [http://dev.w3.org/csswg/css3-values/ CSS Values and Units].
|-
| "legacy-compat"
| -
| Used in HTML for XSLT serializers.
|-
| "srcdoc"
| -
| Used in HTML for its <iframe srcdoc> feature.
|-
| "unicorn"
| A resource whose Content-Type is image/svg+xml and entity body is the contents of [http://html5.org/temp/unicorn.svg unicorn.svg].
| Unicorn!
|}

To '''obtain a resource''' from an about: URL, run these steps:

* If URL's scheme data is not the literal string "blank" or "unicorn", return a network error. (URL's query and URL's fragment are simply not taken into account and can be anything.)
* Return the resource corresponding to the identifier as listed in the table above, with HTTP status code 200 and HTTP status text "OK".

See also [http://tools.ietf.org/html/rfc6694 The "about" URI Scheme] and [http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xml "about" URI Tokens] which this wiki page obsoletes.

=== Examples ===

{| class="wikitable"
|-
! Input
! Result
|-
| about:blanK
| network error (uppercase K)
|-
| about:bl%61nk
| network error (no percent decoding by either the URL parser or the obtain a resource algorithm)
|-
| about:blank?teehee
| works (query does not matter)
|-
| about:blank?teehee#hihi
| works (fragment does not matter either)
|}

== javascript: URLs ==

'''javascript: URLs''' represent a JavaScript script.

To '''obtain a script''' from a javascript: URL, run these steps:

* Let ''input'' be the concatenation of URL's scheme data, followed by "?" and URL's query if URL's query is non-null, followed by "#" and URL's fragment if URL's fragment is non-null.
* Set ''input'' to the result of [http://url.spec.whatwg.org/#percent-decode percent decoding] ''input''.
* If ''input'' starts with a U+FEFF, remove a single occurrence from the start of ''input''.
* Return ''input''.

See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which this wiki page obsoletes.

== data: URLs ==

See [https://www.w3.org/Bugs/Public/show_bug.cgi?id=19494 Bug 19494] and other stuff linked from there.

To '''obtain a resource''' from a [http://url.spec.whatwg.org/#concept-parsed-url parsed URL] whose ''scheme'' is a ASCII case-insensitive match for "data:", run these steps:

* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].
* If the URL’s [http://url.spec.whatwg.org/#concept-url-query query] is not null, append "?" and the query to ''input''.
* If ''input'' does not contain a U+002C COMMA code point, return a network error and abort these steps. (Note: the comma can come either from the scheme data or the query.)
* Split ''input'' at the first comma. Set ''header'' and ''body'' to the parts before and after the comma, respectively. ('''Issue:''' what if the comma is an a MIME quoted string for a parameter value? Example: <code>data:text/plain;foo="bar,baz";charset=utf8,body</code>)
* Set ''body-bytes'' to the result of running ''percent decode to bytes'' on ''body''.
* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
** Remove the matched substring from ''header''
** Decode ''body-bytes'' with the [https://tools.ietf.org/html/rfc4648#section-4 Base 64 Encoding]. ('''Issues:''' Return an error on "invalid" base64? What is invalid? Also accept the ''URL and Filename Safe Alphabet''? Mixed alphabets in the same body? Ignore which non-alphabet bytes? Missing/too little/too much padding?)
* Return a response with ''header'' as a ''Content-Type'' header and ''body-bytes'' as the body. The parsing and interpretation of ''header'' must be the same as for an HTTP ''Content-Type'' header.

To '''percent decode to bytes''', run the same algorithm as '''[http://url.spec.whatwg.org/#percent-decode percent decode]''' but replacing the last step with "Return ''bytes''."

== Others ==

* [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol ws: & wss:]
* See [http://en.wikipedia.org/wiki/URI_scheme Wikipedia]
* See [http://www.iana.org/assignments/uri-schemes.html IANA]

[[Category:Registries]]
[[Category:Spec coordination]]

URL schemes

2012-11-30T16:51:40Z

SimonSapin: /* data: URLs */ Add a link bug 19494

Licensing: this page is under CC0, not the MIT License.

== about: URLs ==

'''about: URLs''' serve as identifier, potentially with an associated resource. The identifier is given in the URL's scheme data.

{| class="wikitable"
|-
! Identifier
! Resource
! Notes
|-
| "blank"
| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
|
|-
| "invalid"
| -
| Used to represent a network error. See also [http://dev.w3.org/csswg/css3-values/ CSS Values and Units].
|-
| "legacy-compat"
| -
| Used in HTML for XSLT serializers.
|-
| "srcdoc"
| -
| Used in HTML for its <iframe srcdoc> feature.
|-
| "unicorn"
| A resource whose Content-Type is image/svg+xml and entity body is the contents of [http://html5.org/temp/unicorn.svg unicorn.svg].
| Unicorn!
|}

To '''obtain a resource''' from an about: URL, run these steps:

* If URL's scheme data is not the literal string "blank" or "unicorn", return a network error. (URL's query and URL's fragment are simply not taken into account and can be anything.)
* Return the resource corresponding to the identifier as listed in the table above, with HTTP status code 200 and HTTP status text "OK".

See also [http://tools.ietf.org/html/rfc6694 The "about" URI Scheme] and [http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xml "about" URI Tokens] which this wiki page obsoletes.

=== Examples ===

{| class="wikitable"
|-
! Input
! Result
|-
| about:blanK
| network error (uppercase K)
|-
| about:bl%61nk
| network error (no percent decoding by either the URL parser or the obtain a resource algorithm)
|-
| about:blank?teehee
| works (query does not matter)
|-
| about:blank?teehee#hihi
| works (fragment does not matter either)
|}

== javascript: URLs ==

'''javascript: URLs''' represent a JavaScript script.

To '''obtain a script''' from a javascript: URL, run these steps:

* Let ''input'' be the concatenation of URL's scheme data, followed by "?" and URL's query if URL's query is non-null, followed by "#" and URL's fragment if URL's fragment is non-null.
* Set ''input'' to the result of [http://url.spec.whatwg.org/#percent-decode percent decoding] ''input''.
* If ''input'' starts with a U+FEFF, remove a single occurrence from the start of ''input''.
* Return ''input''.

See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which this wiki page obsoletes.

== data: URLs ==

See [https://www.w3.org/Bugs/Public/show_bug.cgi?id=19494 Bug 19494] and other stuff linked from there.

To '''obtain a resource''' from a [http://url.spec.whatwg.org/#concept-parsed-url parsed URL] whose ''scheme'' is a ASCII case-insensitive match for "data:", run these steps:

* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].
* If the URL’s [http://url.spec.whatwg.org/#concept-url-query query] is not null, append "?" and the query to ''input''.
* If ''input'' does not contain a U+002C COMMA code point, return a network error. (Note: the comma can come either from the scheme data or the query.)
* Split ''input'' at the first comma. Set ''header'' and ''body'' to the parts before and after the comma, respectively. ('''Issue:''' what if the comma is an a MIME quoted string for a parameter value? Example: <code>data:text/plain;foo="bar,baz";charset=utf8,body</code>)
* Set ''body-bytes'' to the result of running ''percent decode to bytes'' on ''body''.
* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
** Remove the matched substring from ''header''
** Decode ''body-bytes'' with the [https://tools.ietf.org/html/rfc4648#section-4 Base 64 Encoding]. ('''Issues:''' Also accept the ''URL and Filename Safe Alphabet''? Mixed alphabets in the same body? Ignore which non-alphabet bytes? Missing/too little/too much padding?)
* Return a response with ''header'' as a ''Content-Type'' header and ''body-bytes'' as the body. The parsing and interpretation of ''header'' must be the same as for an HTTP ''Content-Type'' header.

To '''percent decode to bytes''', run the same algorithm as '''[http://url.spec.whatwg.org/#percent-decode percent decode]''' but replacing the last step with "Return ''bytes''."

== Others ==

* [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol ws: & wss:]
* See [http://en.wikipedia.org/wiki/URI_scheme Wikipedia]
* See [http://www.iana.org/assignments/uri-schemes.html IANA]

[[Category:Registries]]
[[Category:Spec coordination]]

URL schemes

2012-11-30T16:45:34Z

SimonSapin: /* data: URLs */ Add an example with a comma in a quoted string.

Licensing: this page is under CC0, not the MIT License.

== about: URLs ==

'''about: URLs''' serve as identifier, potentially with an associated resource. The identifier is given in the URL's scheme data.

{| class="wikitable"
|-
! Identifier
! Resource
! Notes
|-
| "blank"
| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
|
|-
| "invalid"
| -
| Used to represent a network error. See also [http://dev.w3.org/csswg/css3-values/ CSS Values and Units].
|-
| "legacy-compat"
| -
| Used in HTML for XSLT serializers.
|-
| "srcdoc"
| -
| Used in HTML for its <iframe srcdoc> feature.
|-
| "unicorn"
| A resource whose Content-Type is image/svg+xml and entity body is the contents of [http://html5.org/temp/unicorn.svg unicorn.svg].
| Unicorn!
|}

To '''obtain a resource''' from an about: URL, run these steps:

* If URL's scheme data is not the literal string "blank" or "unicorn", return a network error. (URL's query and URL's fragment are simply not taken into account and can be anything.)
* Return the resource corresponding to the identifier as listed in the table above, with HTTP status code 200 and HTTP status text "OK".

See also [http://tools.ietf.org/html/rfc6694 The "about" URI Scheme] and [http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xml "about" URI Tokens] which this wiki page obsoletes.

=== Examples ===

{| class="wikitable"
|-
! Input
! Result
|-
| about:blanK
| network error (uppercase K)
|-
| about:bl%61nk
| network error (no percent decoding by either the URL parser or the obtain a resource algorithm)
|-
| about:blank?teehee
| works (query does not matter)
|-
| about:blank?teehee#hihi
| works (fragment does not matter either)
|}

== javascript: URLs ==

'''javascript: URLs''' represent a JavaScript script.

To '''obtain a script''' from a javascript: URL, run these steps:

* Let ''input'' be the concatenation of URL's scheme data, followed by "?" and URL's query if URL's query is non-null, followed by "#" and URL's fragment if URL's fragment is non-null.
* Set ''input'' to the result of [http://url.spec.whatwg.org/#percent-decode percent decoding] ''input''.
* If ''input'' starts with a U+FEFF, remove a single occurrence from the start of ''input''.
* Return ''input''.

See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which this wiki page obsoletes.

== data: URLs ==

To '''obtain a resource''' from a [http://url.spec.whatwg.org/#concept-parsed-url parsed URL] whose ''scheme'' is a ASCII case-insensitive match for "data:", run these steps:

* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].
* If the URL’s [http://url.spec.whatwg.org/#concept-url-query query] is not null, append "?" and the query to ''input''.
* If ''input'' does not contain a U+002C COMMA code point, return a network error. (Note: the comma can come either from the scheme data or the query.)
* Split ''input'' at the first comma. Set ''header'' and ''body'' to the parts before and after the comma, respectively. ('''Issue:''' what if the comma is an a MIME quoted string for a parameter value? Example: <code>data:text/plain;foo="bar,baz";charset=utf8,body</code>)
* Set ''body-bytes'' to the result of running ''percent decode to bytes'' on ''body''.
* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
** Remove the matched substring from ''header''
** Decode ''body-bytes'' with the [https://tools.ietf.org/html/rfc4648#section-4 Base 64 Encoding]. ('''Issues:''' Also accept the ''URL and Filename Safe Alphabet''? Mixed alphabets in the same body? Ignore which non-alphabet bytes? Missing/too little/too much padding?)
* Return a response with ''header'' as a ''Content-Type'' header and ''body-bytes'' as the body. The parsing and interpretation of ''header'' must be the same as for an HTTP ''Content-Type'' header.

To '''percent decode to bytes''', run the same algorithm as '''[http://url.spec.whatwg.org/#percent-decode percent decode]''' but replacing the last step with "Return ''bytes''."

== Others ==

* [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol ws: & wss:]
* See [http://en.wikipedia.org/wiki/URI_scheme Wikipedia]
* See [http://www.iana.org/assignments/uri-schemes.html IANA]

[[Category:Registries]]
[[Category:Spec coordination]]

URL schemes

2012-11-30T16:41:20Z

SimonSapin: Describe parsing of data: URLs. (First pass.)

Licensing: this page is under CC0, not the MIT License.

== about: URLs ==

'''about: URLs''' serve as identifier, potentially with an associated resource. The identifier is given in the URL's scheme data.

{| class="wikitable"
|-
! Identifier
! Resource
! Notes
|-
| "blank"
| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
|
|-
| "invalid"
| -
| Used to represent a network error. See also [http://dev.w3.org/csswg/css3-values/ CSS Values and Units].
|-
| "legacy-compat"
| -
| Used in HTML for XSLT serializers.
|-
| "srcdoc"
| -
| Used in HTML for its <iframe srcdoc> feature.
|-
| "unicorn"
| A resource whose Content-Type is image/svg+xml and entity body is the contents of [http://html5.org/temp/unicorn.svg unicorn.svg].
| Unicorn!
|}

To '''obtain a resource''' from an about: URL, run these steps:

* If URL's scheme data is not the literal string "blank" or "unicorn", return a network error. (URL's query and URL's fragment are simply not taken into account and can be anything.)
* Return the resource corresponding to the identifier as listed in the table above, with HTTP status code 200 and HTTP status text "OK".

See also [http://tools.ietf.org/html/rfc6694 The "about" URI Scheme] and [http://www.iana.org/assignments/about-uri-tokens/about-uri-tokens.xml "about" URI Tokens] which this wiki page obsoletes.

=== Examples ===

{| class="wikitable"
|-
! Input
! Result
|-
| about:blanK
| network error (uppercase K)
|-
| about:bl%61nk
| network error (no percent decoding by either the URL parser or the obtain a resource algorithm)
|-
| about:blank?teehee
| works (query does not matter)
|-
| about:blank?teehee#hihi
| works (fragment does not matter either)
|}

== javascript: URLs ==

'''javascript: URLs''' represent a JavaScript script.

To '''obtain a script''' from a javascript: URL, run these steps:

* Let ''input'' be the concatenation of URL's scheme data, followed by "?" and URL's query if URL's query is non-null, followed by "#" and URL's fragment if URL's fragment is non-null.
* Set ''input'' to the result of [http://url.spec.whatwg.org/#percent-decode percent decoding] ''input''.
* If ''input'' starts with a U+FEFF, remove a single occurrence from the start of ''input''.
* Return ''input''.

See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which this wiki page obsoletes.

== data: URLs ==

To '''obtain a resource''' from a [http://url.spec.whatwg.org/#concept-parsed-url parsed URL] whose ''scheme'' is a ASCII case-insensitive match for "data:", run these steps:

* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].
* If the URL’s [http://url.spec.whatwg.org/#concept-url-query query] is not null, append "?" and the query to ''input''.
* If ''input'' does not contain a U+002C COMMA code point, return a network error. (Note: the comma can come either from the scheme data or the query.)
* Split ''input'' at the first comma. Set ''header'' and ''body'' to the parts before and after the comma, respectively. ('''Issue:''' what if the comma is an a MIME quoted string for a parameter value?)
* Set ''body-bytes'' to the result of running ''percent decode to bytes'' on ''body''.
* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
** Remove the matched substring from ''header''
** Decode ''body-bytes'' with the [https://tools.ietf.org/html/rfc4648#section-4 Base 64 Encoding]. ('''Issues:''' Also accept the ''URL and Filename Safe Alphabet''? Mixed alphabets in the same body? Ignore which non-alphabet bytes? Missing/too little/too much padding?)
* Return a response with ''header'' as a ''Content-Type'' header and ''body-bytes'' as the body. The parsing and interpretation of ''header'' must be the same as for an HTTP ''Content-Type'' header.

To '''percent decode to bytes''', run the same algorithm as '''[http://url.spec.whatwg.org/#percent-decode percent decode]''' but replacing the last step with "Return ''bytes''."

== Others ==

* [http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol ws: & wss:]
* See [http://en.wikipedia.org/wiki/URI_scheme Wikipedia]
* See [http://www.iana.org/assignments/uri-schemes.html IANA]

[[Category:Registries]]
[[Category:Spec coordination]]