- From: Willy Tarreau <w@1wt.eu>
- Date: Wed, 19 Feb 2020 04:29:26 +0100
- To: Roberto Polli <roberto@teamdigitale.governo.it>
- Cc: Rob Sayre <sayrer@gmail.com>, "Roy T. Fielding" <fielding@gbiv.com>, Cory Benfield <cory@lukasa.co.uk>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On Tue, Feb 18, 2020 at 11:33:58PM +0100, Roberto Polli wrote: > >> They have no semantics in the sense that a body cannot change the meaning > >> of a received request. They are absolutely forbidden to have any impact > >> whatsoever on the processing or interpretation of the request aside from > >> the necessity to read and discard the bytes received in order to maintain > >> the message framing. The only reason we didn't forbid sending a body is > >> because that would lead to lazy implementations assuming no body would > >> be sent. > >> > > > > This text on message framing seems clearer to me than what's in the draft, > > but vague references to "semantics" in web specs drive me nuts. Maybe no > > one else cares. :) > > > > I think that the above text should be in the specifications. That will make > the web a better place. Well, it is more or less implied when you check 7230 and 7231 together, but I agree that having such a single prominent sentence somewhere would make it clear to the casual reader that framing requires to support this even though you should not expect to rely on that data. Willy
Received on Wednesday, 19 February 2020 03:29:50 UTC