Re: The case for Content-Unencoded-Length

Am 16.07.2026 um 10:45 schrieb Guoye Zhang:
> Hi,
> 
> We recently enabled zstd support in Safari and received complaints that downloads from a popular cloud storage website are no longer showing progress and no longer resumable. Turns out that they are doing streaming zstd compression so they don’t know the Content-Length.
> 
> Are there interests in standardizing a new header field Content-Unencoded-Length (similar to Unencoded-Digest)? I'm also interested in discussing a new range unit unencoded-bytes for download resumption.
> 
> Thanks,
> Guoye Zhang

How about:

   HEAD /file.bin HTTP/1.1
   Host: example.com
   Accept-Encoding: identity

->

   HTTP/1.1 200 OK
   Content-Length: 5242880

This would be the non-encoded length.

Yes, one additional round trip (but HEAD can be done after starting the 
download), race conditions can be avoided with ETags.

Best regards, Julian

Received on Sunday, 19 July 2026 12:17:21 UTC