- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Sun, 7 Feb 2021 19:55:48 +1300
- To: ietf-http-wg@w3.org
On 7/02/21 2:40 pm, Roy T. Fielding wrote: >> On Jan 31, 2021, at 7:50 PM, Martin Thomson wrote: >> >> This feature has not been implemented and deployed. Worse, this >> feature *cannot* be implemented or deployed as there is no version of >> this protocol, or even an extension to the protocol, that allows this >> feature to be implemented. Every current version either does not >> support trailers (0.9, 1.0) or only supports precisely one trailer >> section (1.1 with chunked encoding, 2, 3). >> >> I appreciate the design as a rational, well-constructed thing. It is >> very crisply defined. However, I don't think that it has any place in >> a document that purports to document an interoperable standard. > > It actually has been implemented and deployed, both within > experimental/hacked > versions of HTTP and within a deployed METADATA extension frame for HTTP/2. > This is not a new concept. E.g., > > https://docs.google.com/document/d/1DsPjl6qWxhcF28vzJey0xQJ2O2eRKHv7CBXt3EZyDjc/ > <https://docs.google.com/document/d/1DsPjl6qWxhcF28vzJey0xQJ2O2eRKHv7CBXt3EZyDjc/> > FTR, Squid core protocol parser has also been refactored over the past few years to handle this type of flexible framing. We use it only for ICAP at present, but can be extended to future HTTP versions relatively easily. So I support leaving this in. Amos
Received on Sunday, 7 February 2021 06:59:37 UTC