Re: The case for Content-Unencoded-Length

> On Jul 17, 2026, at 09:01, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> 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.
> 
> Out of curiosity: how is this different from gzip?
> 
> How would the server know the length if the contents is being streamed???

I suspect that gzip was more CPU and memory intensive so it wasn’t used for live compression during large file transfers.

In this particular case, the size of the file is known ahead of time, but the size after compression isn’t known.

Guoye
> 
>> 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
> 
> 
> Best regards, Julian
> 

Received on Sunday, 19 July 2026 00:04:56 UTC