exceeded the maximum number of rules in the phase http_response_compression: 1 out of 0
What is the issue you’re encountering
Cannot add a compression rule to my cloudflare zone
What steps have you taken to resolve the issue?
Cannot resolve this issue.
I need to disable zstd compression for all http requests from my site because not all browsers support it. However, I am unable to create a compression rule to do this in my dashboard.
It looks like the compression rule limits were recently updated based on the Compression Rules · Cloudflare Rules documentation.
In the last issue, I filled out a form to request a manual compression rule extension for our cloudflare zone, but that limit still hasn’t been applied. I needed to purchase a pro plan for our production domain (simplicitydx.com) to resolve this issue for customers, even though the feature should be available to me on the free plan based on the documentation.
When can I expect our available functionality on the free plan to be in sync with cloudflare’s documentation?
I needed to open up this new issue because the old one is closed. If you could up our compression rule limit, I’d definitely appreciate it! Let me know if you need anything from me to make that happen.
We are gradually rolling out new limits for all customers. The values listed below are the new standard limits, but some customers may still have the previous limits until the rollout is fully completed during the first half of 2025.
Seems to still be delayed rolling out though..
This is unlikely to fix your issue though. Compression is negotiated between the Server (Cloudflare, in this case) and the Client/Browser. The browser says which compression algorithms are supported. Cloudflare won’t send zstd to a client without them explicitly saying it is supported (by including zstd in Accept-Encoding request header). If the header’s entirely missing, they just get uncompressed content. So you’re most likely looking at the wrong solution if you think this is impacting clients. What issues are you having, exactly?
This is not the behavior that we’re seeing. There are certain browsers our clients use that do not specify an Accept-Encoding header, but still receive zstd encoded content even though they can’t support it. The browsers in question are old versions of safari and certain in-app browsers (slack, facebook, instagram, etc).
It appears that cloudflare dynamically chooses the compression based on the file size, since we stopped seeing the compression issue when I disabled zstd encoding on our production domain.
These zones should be already in sync with the new limits, so once you downgrade from Pro most likely you will instantly see the correct limit of 10 free compression rules without any manual intervention. Do let me know if you run into something unexpected though.