Liam
Explore posts from serversCDCloudflare Developers
•Created by Liam on 1/3/2024 in #general-help
GZIPed responses from my origin are being decompressed with `Content-Type: application/octet-stream`
All of them are disabled
5 replies
CDCloudflare Developers
•Created by Liam on 1/3/2024 in #general-help
GZIPed responses from my origin are being decompressed with `Content-Type: application/octet-stream`
And I'd like to avoid the work around of setting a
cache-control: no-transform
as from what I understand this means compressed content would still be sent to users that can't accept it5 replies
CDCloudflare Developers
•Created by Liam on 1/3/2024 in #general-help
GZIPed responses from my origin are being decompressed with `Content-Type: application/octet-stream`
I'm guessing it has something to do with not being on this list https://developers.cloudflare.com/speed/optimization/content/brotli/content-compression/#compression-between-cloudflare-and-website-visitors
But why would that result in the response being decompressed, I would have thought the supported list would only being for compressing responses not already compressed at the origin.
5 replies
CDCloudflare Developers
•Created by Liam on 12/31/2023 in #general-help
`Accept-Encoding` received by origin is not what was sent by the user
nope, should i just use gzip then?
4 replies
CDCloudflare Developers
•Created by Liam on 12/31/2023 in #general-help
`Accept-Encoding` received by origin is not what was sent by the user
Without
cache-control: no-transform
the compressed body stays the same and gets to the user fine but the content-encoding
header gets stripped.4 replies
CDCloudflare Developers
•Created by Liam on 12/31/2023 in #general-help
`Accept-Encoding` received by origin is not what was sent by the user
I am returning
cache-control: no-transform
which at least allows the content-encoding: deflate
header to get through, however I still cannot access the users Accept-Encoding
header.4 replies