X-Gateway-Skip-Cache
The unofficial X-Gateway-Skip-Cache response header carries the boolean a hosting-side gateway evaluated when deciding whether to cache the response. The header belongs to a four-header family beside X-Gateway-Cache-Status, X-Gateway-Cache-Key, and X-Gateway-Request-ID on WordPress hosting behind Cloudflare.
Usage
The flag and the verdict move together in every
crawled response: 1 pairs with a BYPASS cache
status, 0 with the cacheable verdicts (MISS,
HIT, EXPIRED). Reading the flag answers whether
a bypass came from the gateway's own rules rather
than from an empty cache, the same distinction
nginx deployments express through
fastcgi_cache_bypass variables.
WordPress responses trigger the skip through
logged-in cookies, carts, and session state, which
is why 1 dominates crawled traffic: the crawl
lands on plenty of pages the gateway refuses to
store for anyone.
Values
1
The gateway skipped its cache for the request, and the response was neither served from nor written to the cache.
0
Caching applied, and the companion status reports the lookup outcome.
Example
A response the gateway refused to cache, with the companion verdict spelling out the consequence.
HTTP/1.1 200 OK
X-Gateway-Skip-Cache: 1
X-Gateway-Cache-Status: BYPASS