⌘K
Profile
@usernameMember since January 2020
@azeitlerMember since August 2025No badges yet
No accepted solutions yet
BREAKING CHANGE: pre-compressed assets re-compressed at the edge
@swarnava Any news on my issue? (because its different from @mihakrajnc’s and your answer does not cover it)
BREAKING CHANGE: pre-compressed assets re-compressed at the edge
Any news on my issue (because its different from @mihakrajnc's and your answer does not cover it)
BREAKING CHANGE: pre-compressed assets re-compressed at the edge
@swarnava also jumping in here. Any news? The issue is still blocking us from Vercel for additional projects.
BREAKING CHANGE: pre-compressed assets re-compressed at the edge
@pawlean any update on this? Is this new default behaviour? Safari still cannot handle the double encoding.
BREAKING CHANGE: pre-compressed assets re-compressed at the edge
A related problem was reported in October 2024 https://community.vercel.com/t/vercel-not-serving-pre-compressed-assets-brotli/1639 The user even provided a demo repository, but...
BREAKING CHANGE: pre-compressed assets re-compressed at the edge
Here you go: https://github.com/azeitler/wasm-compression-issue Starting at a 100kb file-size .br files are now compressed again and a second `br` Content-Encoding header is added...
BREAKING CHANGE: pre-compressed assets re-compressed at the edge
It seems due to a recent change pre-compressed assets, eg file.ext.br, are re-compressed at the edge, with an additional Content-Encoding header added, resulting in...