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. -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
