cache miss due to fetch redirect?
Hi! I am trying to create a worker to proxy a custom origin.
The origin first responds with a 307 redirect, which changes dynamically. When the redirect is followed, the origin delivers the document.
The problem is that I cannot get cloudfare fetch to cache; and I'm not sure how to debug it or what else to try... Maybe it's because of the redirect? Or maybe because of the cache-control headers coming from the origin? I'm stumped. When I hit my worker repeatedly, I get the following headers (the worker sends back cf-ray and cf-cache-status from its origin fetch) Here's what the origin returns when curled directly:
The problem is that I cannot get cloudfare fetch to cache; and I'm not sure how to debug it or what else to try... Maybe it's because of the redirect? Or maybe because of the cache-control headers coming from the origin? I'm stumped. When I hit my worker repeatedly, I get the following headers (the worker sends back cf-ray and cf-cache-status from its origin fetch) Here's what the origin returns when curled directly:
1 Reply
hello Isaac, did you find a solution?