It's probably worth calling out that all caches in the serving path will need to support Vary: sec-bikeshed-available-dictionary so that the cache for a given URL doesn't get polluted with delta-compressed artifacts using different dictionaries.
Full Vary support for arbitrary headers isn't necessarily needed but it will be required for whatever the dictionary request header ends up being.
Not sure if it needs specific mentioning, but this is for the CDNs, Load balancers and web servers at a minimum, depending on what caches are in the path for a given origin.
I'm assuming it also needs to be limited to HTTPS (and maybe only HTTP/2 and 3) to reduce the risk of forward proxies or intercepting man-in-the-middle proxies from causing cache issues.
It's probably worth calling out that all caches in the serving path will need to support
Vary: sec-bikeshed-available-dictionaryso that the cache for a given URL doesn't get polluted with delta-compressed artifacts using different dictionaries.Full Vary support for arbitrary headers isn't necessarily needed but it will be required for whatever the dictionary request header ends up being.
Not sure if it needs specific mentioning, but this is for the CDNs, Load balancers and web servers at a minimum, depending on what caches are in the path for a given origin.
I'm assuming it also needs to be limited to HTTPS (and maybe only HTTP/2 and 3) to reduce the risk of forward proxies or intercepting man-in-the-middle proxies from causing cache issues.