"cacheEverything: true" causes Accept-Encoding header from CF->origin to be blank

What is the name of the domain?

What is the issue you’re encountering

When I add a “Cache Everything” cache rule, it causes all requests that hit the rule to not be compressed from origin->CF, due to the accept-encoding header not being present

What steps have you taken to resolve the issue?

Hi! I have been chasing down a confusing increase of origin bandwidth, and it looks to me like the culprit is that at least for some of our zones, setting a “Cache Everything” rule (either through Cache Rules, or cacheEverything: true in a worker) causes the resulting request from Cloudflare->Origin to lose the Accept-Encoding: gzip,br header that is normally used for all CF->origin requests.

Is this intended behavior? A bug? Has anyone encountered anything like this before? The CF docs say

On all plans, Cloudflare requests content from the origin server using the accept-encoding: br, gzip

To make things more confusing, doing a second request to precisely the same URL (still with the Cache Everything rule) will have the proper Accept-Encoding header to origin

GET /?foo=bar123 -
GET /?foo=bar123 - Accept-Encoding: gzip, br
GET /?foo=bar234 -

I am a bit baffled by the behavior. Hoping there’s some simple thing I have misconfigured, but I’ve tested it in a variety of different zones, different types of origin servers, etc.

Hi, sorry for the issues that you’re facing.

Could you please submit a support ticket with us and share some further origin logs over it to help with debugging?

Thank you

This topic was automatically closed after 15 days. New replies are no longer allowed.