- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Wed, 22 Oct 2025 05:14:46 +1300
- To: ietf-http-wg@w3.org
On 21/10/2025 13:11, Mark Nottingham wrote:
> Hi Rory,
>
>> On 21 Oct 2025, at 10:59 am, Rory Hewitt wrote:
>>
>> But if an entity wants to indicate either of the following:
>>
>> * a stream MUST NOT be buffered, and a proxy must throw an error if it requires buffering
>> * a stream MUST be buffered, and a proxy must throw an error if is cannot buffer the stream
>>
>> what options will it have to indicate that?
>
> Making it a MUST is not backwards-compatible with HTTP semantics, so I don't think it's on the table as a possibility.
>
I get that the legacy installed agents will not follow a new feature.
But agents implementing this feature/extension can still be required
with MUST emit a 503 when they have to buffer a message with ?1 set.
Supporting agents then treat the {?1, ?0, missing} triplet essentially
as {MUST, SHOULD NOT, MAY} relay incrementally.
Cheers
AYJ
Received on Tuesday, 21 October 2025 16:14:54 UTC