`Accept-Encoding` received by origin is not what was sent by the user

I'd like to handle the compression of my content myself as the files are relatively large (~20mb avg). I have setup deflate compression on my server which works great (compresses down to ~5mb) however I have no way of disabling it when the user doesn't support it as the Accept-Encoding header received on the server only has gzip listed even though I am sending the request with postman with Accept-Encoding: gzip, deflate, br. Even when setting Accept-Encoding: deflate the origin only receives gzip in the header. How can I make sure I am getting the same Accept-Encoding header at my server that is being sent from the user? I just want cloudflare to act as a proxy to protect my server, I don't want any fancy compression stuff.
1 Reply
Liam
Liam6mo ago
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. Without cache-control: no-transform the compressed body stays the same and gets to the user fine but the content-encoding header gets stripped. nope, should i just use gzip then?