Yeah, cool shit Caddy, just yeet the Content-Length from random files for no reason

volpeon@icy.wyvern.rip

@forst @lnkr Wait, you're saying that Caddy is compressing the file itself even though I added a precompressed one? What the fuck

forst@mastodon.social

@volpeon @lnkr Correct, that's my current hypothesis. Content-Length would be unknown at the start of the transfer, since it's compressing on the fly.

jbauer@merveilles.town

@volpeon > You can verify both are precompressed by appending ".br".

BRAZIL MENTIONED

volpeon@icy.wyvern.rip

@jbauer

volpeon@icy.wyvern.rip

@forst @lnkr

I think Caddy is serving the precompressed file after all. I ran

curl -so /dev/null "https://volpeon.ink/_astro/about.ArvwJ6Ft.css.br" -w '%{size_download}'
curl -so /dev/null "https://volpeon.ink/_astro/about.ArvwJ6Ft.css" -H "Accept-Encoding: br" -w '%{size_download}'

and both commands yielded the same size.

NodeBB

Yeah, cool shit Caddy, just yeet the Content-Length from random files for no reason