Better integration with HTTP Reverse Proxies
Profiling with Blackfire requires requests to hit the server, not caches or reverse proxies.
When using an HTTP cache, your applications are faster as your code is executed less often. But as a consequence, you cannot easily profile your code anymore as Blackfire will mostly hit the cached page instead of your application servers.
If you are using Varnish or Fastly, we provide a VCL snippet that allows Blackfire to bypass the cache.
If you are using Cloudflare, it is a bit more complicated as you can only configure cache activation using page rules based on URLs, not headers as required by Blackfire. But there is a solution, which uses Cloudflare’s workers.