workers-help
pages-help
general-help
durable-objects
workers-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
âš¡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
Workers returning cache hit for 500 response without cache headers
I have a remix application deployed to cloudflare pages. We recently had a scenario where some unexpected load was generated against our API which caused an outage. The specifics of this are still being investigated, but as this happened we found that the remix application took longer to recover than the API itself. From what we can see the 500 response from the worker as a result of the api outage had been cached and as such the cached response continued to be returned after the API recovered.
I have attached a screenshot of the response. We cannot see any specific details of the response that would indicate that it should be cached like a cache-control or expires header. We currently have a very rudimentary implementation of the cache api within our worker function which we suspect needs to be updated to avoid this. However I have been unable to find any documentation explaining the condition which is causing it to be cached making it difficult to know what changes exactly are required. Ideally we would just like our cache implementation to match the behaviour of cloudflare when not using workers. I'm not sure how practical that is though. I have attached our worker entry point for reference as well....
Wildcard DNS + Worker + R2 custom domain
Hi,
I have a wildcard DNS set
AAAA * 100:: and a worker with route *domain.com/*; my worker handles all requests to domain.com and any subdomain user1.domain.com. I've enabled a custom domain for an R2 bucket at assets.domain.com; the Cloudflare dashboard said "You currently have a wildcard record for *.domain.com. While the record will remain, requests to assets.domain.com will now be served from your R2 bucket.". The entry for R2 indeed appeared on the DNS configuration page. However, requests to assets.domain.com are still directed to the worker. How can I resolve this? I need the worker to continue handling all subdomain requests except for assets. Thanks....