You will find that there is indeed a definition. The abnf permits token and quoted-string. But the actual value is a sequence of octets. If this were another protocol I would use Unicode strings. On 8 Jun 2016 4:55 PM, "Poul-Henning Kamp" <phk@phk.freebsd.dk> wrote: > -------- > In message <5757BCD5.4060204@ecaspia.com>, Craig Pratt writes: > > > There's "token", defined in RFC 7230. It allows some punctuation > > characters, but it's certainly more restricted than 1*OCTET. > > That is probably going too far the other way since it doesn't allow > ':' and therefore cannot contain a URL. > > Maybe the "quoted-string" from RFC7230 3.2.6 ? > > quoted-string = DQUOTE *( qdtext / quoted-pair ) DQUOTE > qdtext = HTAB / SP /%x21 / %x23-5B / %x5D-7E / obs-text > obs-text = %x80-FF > quoted-pair = "\" ( HTAB / SP / VCHAR / obs-text ) > > r maybe simply point at RFC7230 3.2.6, since that talks about > HTTP headers in general ? > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > >
Received on Wednesday, 8 June 2016 07:16:58 UTC