Http/2 Proxy Issue
- They should know their Apache config has an HTTP/2 proxy issue The fact that enabling HTTP/2 to Origin in Cloudflare breaks the Apache → Varnish routing is a platform bug on their side. Other Cloudways customers using Cloudflare with Varnish will have the exact same problem without knowing it. Worth flagging so they can fix it properly in their Apache VCL configuration rather than relying on HTTP/2 to Origin being disabled as a workaround.
- It's a workaround, not a proper fix Disabling HTTP/2 to Origin works, but HTTP/2 has real performance benefits — multiplexed connections, header compression, faster connection establishment. Ideally Cloudways should fix their Apache configuration so Varnish works correctly with HTTP/2 connections from Cloudflare, giving you both benefits simultaneously.
- It could break again If anyone re-enables HTTP/2 to Origin in Cloudflare in future — you, a developer, or even a Cloudflare default change — Varnish will silently stop working again with no obvious indication. Having Cloudways fix the root cause means you're not dependent on that one Cloudflare toggle staying off. What To Tell Them Simplify the ticket to: "HTTP/2 to Origin in Cloudflare causes Apache to bypass Varnish completely on application Disabling HTTP/2 to Origin resolves it. Please fix the Apache → Varnish proxy configuration to handle HTTP/2 connections correctly so both can work simultaneously." It's a quick flag rather than an urgent support request now — but worth having on record with them.
1
vote
Ian Blackwood
shared this idea