Cloudflare swallows cache header?

I have…

  • [ ] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • [x] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

Sending a cache header when requesting assets does not set Cache-Control header.

Expected behavior

According to the documentation sending a cache header should result in the response containing a Cache-Control header in the response with maxAge set to the sent cache value.

But it looks like Cloudflare swallows this and the Cache-Control header isn’t in the response. Is this feature still supposed to be supported in the cloud version of Squidex / Squidex instances with a CDN?

Minimal reproduction of the problem

  1. Request an asset on squidex cloud and set the cache header
  2. Observe the response: it doesn’t contain the Cache-Control header


  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [x] Cloud version

Version: N/A


  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge
  • [x] Android native client (with Apollo graphQL library)

I cannot reproduce it:

I think you have misunderstand the documentation. The docs talk about

cache query parameter

Oy, yeah, bummer. I’m very sorry about that! :pray:

1 Like