Re: #305 Header ordering

On 22/11/2013 2:57 p.m., Roberto Peon wrote:
> All of the proposals handle any potential nondeterminism amongst header
> fields with the same name, so that isn't a problem...
> -=R

Also keep in mind that 1.1->2.0 and 2.0->2.0 software is all going to be
fresh code. If the spec is clear enough on where multiple values are to
be found and how to handle there is no excuse for this mess to continue
outside of legacy 1.1 connections.


Received on Friday, 22 November 2013 14:19:23 UTC