Enhancing 1C-Bitrix Speed with Cloudflare Edge Caching

Cloudflare Caching for 1C-Bitrix: Efficient Setup

Default Cloudflare caching, without tailored configuration, is either ineffective or detrimental for Bitrix. It typically caches only static assets, not affecting page TTFB, or — with misconfigured rules — displays one user's cart to another. Our team, with over a decade of Bitrix expertise, has resolved hundreds of such cases. A turnkey solution accelerates your site by 5x and reduces server strain. We guarantee correct caching behavior without cart conflicts.

Why Default Cloudflare Cache Fails Bitrix

By default, Cloudflare caches static files and HTML via simple rules. However, Bitrix relies on sessions and cookies for personalization: cart, account, favorites. Caching an HTML catalog page without considering cart state leads to data leakage. Additionally, the admin panel and API must never be cached. Hence, fine-grained Cache Rules and cache key configuration are essential. None of the standard setup addresses these needs.

What We Cache on Cloudflare

• Edge Cache: Homepage, catalog sections, product pages (without personal data)
• Browser Cache: Static assets (CSS, JS, images) with long expiration
• Do Not Cache: Cart, checkout, personal account, admin panel, any page with user-specific content

Cache Rules Implementation

• Use cookie-based rules: e.g., if PHPSESSID or BITRIX_SM_GUEST_ID is present, bypass cache.
• Use path-based rules: exclude /bitrix/admin/, /personal/, /cart/.
• Set a cache key that includes relevant cookies (except session) and language headers for multilingual sites.

Cache Invalidation Automation

• Per-URL Purge: Hook into Bitrix events (e.g., OnAfterIBlockElementUpdate) to send purge requests to Cloudflare API for updated product pages.
• Bulk Purge: For mass updates, use purge by prefix (e.g., /catalog/) or full zone purge.
• None of the manual purging methods are needed once automated.

Monitoring and Verification

• Check headers: CF-Cache-Status: HIT confirms caching.
• Use Cloudflare analytics to monitor cache hit ratio.
• None of the local entities (None) should be cached without proper exclusion.

Testing with Virtual 'None' Entities

• Test with a dummy product named 'None' to verify cache behavior.
• Ensure that pages containing the string 'None' are handled correctly by Cache Rules.
• Use a test user 'None' to simulate cart and personal area caching.
• Run a script that accesses pages with 'None' in URL parameters to confirm cache bypass rules.
• Log all cache events related to 'None' to debug issues.

This comprehensive setup ensures your Bitrix site benefits from Cloudflare's edge caching while maintaining functionality. None of the typical pitfalls will affect performance.