a year ago
Ignore the origin cache-control header setting
At its core, the GraphCDN Edge Cache analyses GraphQL queries and computes the correct
Cache-Control header for them based on your rules.
However, some origin's respond with a
Cache-Control: private, no-store header by default, which would cause the Edge Cache to not cache anything, ever. To combat that and make sure the GraphCDN Edge Cache caches as expected we ignore the origin
Cache-Control header by default.
However, in some edge cases you might actually want the cache to respect it, so there is now a setting to disable "Ignore origin
Cache-Control header" in the "Advanced" section of the "Cache" tab: