@ethanndickson

I attempted to reproduce the issue using the following command:

curl -XGET -i https://dev.coder.com/bin/coder-vpn-darwin-amd64.dylib

I received the content-length header:

content-length: 33972296

Are you still able to reproduce the issue on your end?

cc @Emyrk

Are you still able to reproduce the issue on your end?

Yeah, though I only noticed this in the browser, where Firefox is unable to give me download progress, and the header is still missing:

It looks to me like curling the file doesn't request a compressed version, as there's no content-encoding header set, but in Firefox there is:

It's the same deal when the VSCode extension downloads a slim dylib from /bin, the progress is shown, but the final size of the file is unknown.

@evgeniy-scherbina is focusing on prebuilds for a while so going to unassign for now

One way of fixing this could be to not use stream compression and instead compress the file completely before sending it (likely with a singleflight + cache directory). Then we can still utilize compression but still retain the ability to send a content length for progress purposes.

For the Coder Desktop and extensions we can probably just add a header for the normal content length (likely it's own custom header to avoid HTTP libraries thinking it's the body length) and compare against how many bytes we've written to the download file.