Re: Working Group Last Call: Encrypted Content-Encoding for HTTP

On 8/06/2016 6:50 p.m., Poul-Henning Kamp 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 ?
> 

Why the pick between them? isn't there an ongoing WG intention to make
field-values more consistently a generic:

 token BWS "=" BWS ( token / quoted-string )


Amos

Received on Wednesday, 8 June 2016 07:18:49 UTC