At the moment the site operator has three choices: * bundle two separate archives, one with compression and one without (provided it fits in 4 GiB), and use so

At the moment the site operator has three choices: * bundle two separate archives, one with compression and one without (provided it fits in 4 GiB), and use something like HAProxy to choose between the two backends based on the Accept-Encoding header; * (most likely) use a CDN service (like CloudFlare) that would do caching and re-encoding based on what the actual client supports; * choose to just support compressed contents, based on the next observation; Any "modern enough browser" (say since 2018, and here I include things like Netsurf), does support even Brotli compression, let alone gzip. Indeed Lynx (the console browser) doesn’t support Brotli, but it still does support gzip. Thus, for all "real clients" out there, serving straight compressed contents is not an issue, thus one could choose to just ignore the Accept-Encoding header.