Re: [Last-Call] Last Call: <draft-ietf-httpbis-header-structure-18.txt> (Structured Field Values for HTTP) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 15.05.2020 18:06, Poul-Henning Kamp wrote:
--------
In message <4859a11f-5649-b633-f43b-facf036e61c7@xxxxxx>, Julian Reschke writes
:

Related to this: it just occurred to me that:

   Test: Foo
   Test:
   Test: Bar

yields different results for fields using HTTP's list notation, and
structured header fields.

In the former case, the combined value is equivalent to

   Test: Foo, Bar

while in the latter case, the field is malformed.

I *really* think it would be better if structured header fields would
actually be "proper" applications of the standard HTTP list ABNF.

Considering how rarely used multiple-headers are (apart from The
Cookie Mistake) I think it would be much simpler, better and wiser
to restrict SH to single, non-concatenated headers.

I have no idea what the exact proposal would be. Fail when multiple
instances are there?

...

Best regards, Julian

--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux