- From: Lars G. Svensson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Sep 2019 09:27:38 +0000
- To: public-dxwg-wg@w3.org
@rob-metalinkage scripsit:
> ... if we can use URIs as token values legally
[RFC 7230 ยง3.2.6](https://tools.ietf.org/html/rfc7230#section-3.2.6) defines `token` as follows:
> Most HTTP header field values are defined using common syntax
components (token, quoted-string, and comment) separated by
whitespace or specific delimiting characters. Delimiters are chosen
from the set of US-ASCII visual characters not allowed in a token
(DQUOTE and "(),/:;<=>?@[\]{}").
>
> token = 1*tchar
>
> tchar = "!" / "#" / "$" / "%" / "&" / "'" / "*"
> / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
> / DIGIT / ALPHA
> ; any VCHAR, except delimiters
That means that URIs cannot be used as tokens since e. g. the colon character is not allowed in tokens.
--
GitHub Notification of comment by larsgsvensson
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/501#issuecomment-527075307 using your GitHub account
Received on Monday, 2 September 2019 09:27:40 UTC