5 ms·

I'm having this same issue and have a ticket open with cloudflare enterprise support -- started this morning just after cloudflare performed maintenance on thei

I'm having this same issue and have a ticket open with cloudflare enterprise support -- started this morning just after cloudflare performed maintenance on their DNS. No response from ENT support yet. Opening a ticket with netlify too. for now i've simply put a cloudflare page rule up to bypass cache.

frabjoused 4y ago
Interesting. The fact that we both have CF/Netlify as a stack seems to point more to Netlify and CF is just caching it. We similarly bypassed the CF cache for now and opened tickets with both.
- notlify 4y ago
  Agreed, I can't seem to reproduce with netlify directly though, have a small script checking it now. Will report back if i hear anything
  - notlify 4y ago
    Got confirmation from cloudflare support that the `hello` response originated from netlify. netlify support predictably blamed cloudflare without any proof.
dknecht 4y ago
Can you send me your ticket? dane AT cloudflare
- notlify 4y ago
  sure thing, forwarded