hopefully! I feel like I'm gonna have to end up doing a Cron Worker eventually anyway to handle edge
hopefully! I feel like I'm gonna have to end up doing a Cron Worker eventually anyway to handle edge cases.
Content-Encoding: gzip when uploading, that way CF can automatically decompress it for clients that don't support gzip too.cache-control: no-transform, which blocks CF from decompressing it
no-transform set. https://azure-di.6873d51718aa43a6389a532434554150.r2.cloudflarestorage.com/2024-02-29-preview/prebuilt-read/a45b747b5ed4c37de569213aef10649a.json?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=022cbef64017d6c3154435aeb62aeac1%2F20240403%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20240403T150153Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=b09dd0376defa5ce6ea683f2469304e877bc99d5626bb5c0266b3f3fa8d4a0d1Vary: Accept-Encoding in the response header is wrong afaik, since with Cache-Control: no-transform, the response won't vary at all. Cache-Control: no-transform cache-control after you've already uploaded a bunch of files, you can use aws4fetch to make a presigned URL with ?response-content-encoding=blahblah set to override it.