- From: Martin Thomson <mt@lowentropy.net>
- Date: Thu, 27 Feb 2025 11:28:46 +1100
- To: "Roy Fielding" <fielding@gbiv.com>, last-call@ietf.org
- Cc: draft-ietf-httpbis-cache-groups@ietf.org, "Francesca Palombini" <francesca.palombini@ericsson.com>, httpbis-chairs@ietf.org, ietf-http-wg@w3.org, "Tommy Pauly" <tpauly@apple.com>
On Thu, Feb 27, 2025, at 06:05, Roy T. Fielding wrote: > While doing a header field review I ran across the below requirements in > sections 2 (Cache Groups) and 3 (Cache-Group-Invalidation). > Implementations MUST support at least 128 groups in a field value, > with up to at least 128 characters in each member. Note that generic > limitations on HTTP field lengths may constrain the size of this > field value in practice. > Why would we want to require implementations to support that many? > What is the protocol interoperability problem that this is trying to solve? You make a compelling case for some reduction here. It seems like this would work with a much lower limit, such as the 24x64 you suggest. Even that is nearly 2kB.
Received on Thursday, 27 February 2025 00:29:30 UTC