- From: Julian Reschke <julian.reschke@greenbytes.de>
- Date: Wed, 29 Apr 2015 19:04:59 +0200
- To: "henry.story@bblfish.net" <henry.story@bblfish.net>, Willy Tarreau <w@1wt.eu>
- CC: Michael Sweet <msweet@apple.com>, Eric Covener <covener@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2015-04-29 18:53, henry.story@bblfish.net wrote:
> ...
>> Well you can use it between your own components, but you'll have a hard
>> time explaining to all your users that their freshly acquired products
>> which used to respect standard still 2015 are not standard-compliant
>> anymore past 2015. At least with Upgrade we had the ability to play on
>> the compliance side to convince vendors to fix their crap and sell their
>> fixes as feature updates ("support for websocket and HTTP/2").
>
> Again defining something that is undefined does not break a standard.
> The latest spec says that GET can have Content-Length header. Presumably
> the people allowing this had their reasons. Perhaps this is it.
> ...
Or perhaps it is not. The "people allowing this" are over here, and we
have an issue tracker related to that change that I already pointed to
(<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/19>).
Best regards, Julian
Received on Wednesday, 29 April 2015 17:05:26 UTC