W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2020

Re: draft-ietf-httpbis-header-structure-15.txt, 4.1.6. Serializing a String

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 18 Feb 2020 15:53:00 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@varnish-cache.org>
Message-Id: <952D5261-26B7-419E-8987-FA10125C63A4@mnot.net>
To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
Hi Kari,

> On 17 Feb 2020, at 4:38 am, Kari Hurtta <hurtta-ietf@elmme-mailer.org> wrote:
> 
> 4.1.6.  Serializing a String
> https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-15#section-4.1.6
> 	
> 
> Output is restricted ASCII, but this alogrithm seems not say that
> input_string is limited to ASCII
> 
> |   Given a string as input_string, return an ASCII string suitable for
> |   use in a HTTP header value.
> |
> |   1.  If input_string is not a sequence of characters, or contains
> |       characters in the range %x00-1f or %x7f (i.e., is not in VCHAR or
> |       SP), fail serialisation.
> 
> In other words, should this fail serialization if input_string is not
> ASCII string ?

That's one of the effects of this step, yes. See the definition of the string data type at:
  https://httpwg.org/http-extensions/draft-ietf-httpbis-header-structure.html#string


> Now failing is implicit, because there is just
> 
> |       2.  Append char to output.
> 
> And if char is not ASCII then "return an ASCII string" part
> is violated.
> 
> / Kari Hurtta
> 

--
Mark Nottingham   https://www.mnot.net/
Received on Tuesday, 18 February 2020 04:53:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 18 February 2020 04:53:23 UTC