URL schemes - Revision history

Domenic: /* about: URLs */ Add html-kind

2020-08-11T19:31:34Z

about: URLs: Add html-kind

← Older revision		Revision as of 19:31, 11 August 2020
Line 18:		Line 18:
	\| -		\| -
	\| Used by CSS's url() function as a default value		\| Used by CSS's url() function as a default value
			\|-
			\| [https://html.spec.whatwg.org/#about:html-kind "html-kind"]
			\| -
			\| Used as an identifier for kinds of media tracks for HTML <audio> and <video> elements.
	\|-		\|-
	\| [https://html.spec.whatwg.org/#about:legacy-compat "legacy-compat"]		\| [https://html.spec.whatwg.org/#about:legacy-compat "legacy-compat"]
Line 28:		Line 32:
	\|}		\|}

	about: URLs are handled as [https://fetch.spec.whatwg.org/#scheme-fetch part of the Fetch Standard]. Cases like about:config can also make it to the fallback paths of HTML's [https://html.spec.whatwg.org/#navigate navigate] algorithm.		about: URLs are handled as [https://fetch.spec.whatwg.org/#scheme-fetch part of the Fetch Standard]; all but about:blank cause a network error. Cases like about:config can also make it to the fallback paths of HTML's [https://html.spec.whatwg.org/#navigate navigate] algorithm.

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

Domenic at 19:29, 11 August 2020

2020-08-11T19:29:47Z

← Older revision		Revision as of 19:29, 11 August 2020
Line 14:		Line 14:
	\| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.		\| A resource whose Content-Type is text/html;charset=utf-8 and entity body is the empty string.
	\|		\|
			\|-
			\| [https://drafts.csswg.org/css-values-3/#about-invalid "invalid"]
			\| -
			\| Used by CSS's url() function as a default value
	\|-		\|-
	\| [https://html.spec.whatwg.org/#about:legacy-compat "legacy-compat"]		\| [https://html.spec.whatwg.org/#about:legacy-compat "legacy-compat"]

Domenic: Reference modern documents and specs

2020-08-11T19:27:38Z

Reference modern documents and specs

← Older revision		Revision as of 19:27, 11 August 2020
Line 15:		Line 15:
	\|		\|
	\|-		\|-
	\| ~~"invalid"~~		\| [https://html.spec.whatwg.org/#about:legacy-compat "legacy-compat"]
	~~\| -~~
	~~\| 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.		\| Used in HTML for XSLT serializers.
	\|-		\|-
	\| "srcdoc"		\| [https://html.spec.whatwg.org/#about:srcdoc "srcdoc"]
	\| -		\| -
	\| Used in HTML for its <iframe srcdoc> feature.		\| 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~~:		about: URLs are handled as [https://fetch.spec.whatwg.org/#scheme-fetch part of the Fetch Standard]. Cases like about:config can also make it to the fallback paths of HTML's [https://html.spec.whatwg.org/#navigate navigate] algorithm.

	* 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.		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.
Line 61:		Line 50:
	== data: URLs ==		== data: URLs ==

	See ~~http~~://~~simonsapin~~.~~github~~.~~com~~/data-~~urls/~~		See [https://fetch.spec.whatwg.org/#data-url-processor the Fetch Standard]

	== javascript: URLs ==		== javascript: URLs ==

	'''javascript: URLs''' represent a JavaScript script.		'''javascript: URLs''' represent a JavaScript script. They are handled by the HTML Standard's [https://html.spec.whatwg.org/#javascript-protocol navigate algorithm].

	~~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.		See also [http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme The 'javascript' resource identifier scheme] which the HTML Standard obsoletes.

	== Others ==		== Others ==

GPHemsley: +{{CC0 page}}

2013-02-20T18:44:54Z

+{{CC0 page}}

← Older revision		Revision as of 18:44, 20 February 2013
Line 1:		Line 1:
	~~Licensing: this~~ page ~~is under CC0, not the MIT License.~~		{{CC0 page}}

	== about: URLs ==		== about: URLs ==

Annevk: abc

2012-12-02T23:52:09Z

abc

← Older revision		Revision as of 23:52, 2 December 2012
Line 58:		Line 58:
	\| works (fragment does not matter either)		\| works (fragment does not matter either)
	\|}		\|}

			== data: URLs ==

			See http://simonsapin.github.com/data-urls/

	== javascript: URLs ==		== javascript: URLs ==
Line 71:		Line 75:

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

	~~== data: URLs ==~~

	~~See http://simonsapin.github.com/data-urls/~~

	== Others ==		== Others ==

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

2012-12-02T09:58:20Z

data: URLs: Moved to GitHub.

@@ Line 74: / Line 74: @@
 == 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]
+See http://simonsapin.github.com/data-urls/
 == Others ==

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

2012-12-01T21:20:08Z

data: URLs: Add a TODO for missing parsing steps

← Older revision		Revision as of 21:20, 1 December 2012
Line 74:		Line 74:
	== data: URLs ==		== data: URLs ==

	See [https://www.w3.org/Bugs/Public/show_bug.cgi?id=19494 Bug 19494] and other stuff linked from there.		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:		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:
Line 87:		Line 87:
	** 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?)		** 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?)		* 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.		'''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.

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

2012-11-30T17:13:58Z

data: URLs: Allow (and suggest) some optimization.

← Older revision		Revision as of 17:13, 30 November 2012
Line 87:		Line 87:
	** 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?)		** 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?)		* 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''."		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''."

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

2012-11-30T17:01:47Z

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

← Older revision		Revision as of 17:01, 30 November 2012
Line 86:		Line 86:
	** Remove the matched substring from ''header''		** 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?)		** 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.		* 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''."		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''."

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

2012-11-30T16:55:18Z

data: URLs: Expand on errors and invalid base64

← Older revision		Revision as of 16:55, 30 November 2012
Line 80:		Line 80:
	* Set ''input'' to the URL’s [http://url.spec.whatwg.org/#concept-url-scheme-data scheme data].		* 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 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.)		* 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>)		* 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''.		* 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:		* If ''header'' ends with ";base64" ('''Issue:''' Match how strictly? Case sensitive or not? Allow whitespace? Percent-encoding?) then:
	** Remove the matched substring from ''header''		** 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?)		** 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.		* 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.