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
Dynamic dispatch worker call multiple user workers?
Cloudflare warp not working
Microsoft Edge marks Cloudflare's Worker edit/preview page as unsafe
Require JSON output from Workers AI?
TypeScript - Reflect-Metadata decorators being omitted from bundle
what's the point of workers?
Shared logic between NextJS app or duplicate the logic?
Worker orchestration idea might be overkill
Env ,Variables in Github Workflow
Rate Limit not defined on env
How to maintain WebSocket client connections in Durable Object?
Migration from KV to D1
Too many API requests by single worker invocation
. I understand that internal calls to certain services are limited to 1000. Is there any way to temporarily increase this in order to make the migration process easier?
Worst case I can limit the amount of items interacted with, but this is a little more tedious than just being able to migrate it all at the same time....Per-Deployment Secrets?
Plans to support MongoDB?
responses with "cf-cache-status: REVALIDATED" are being stored in cache following fetch()
cf-cache-status: REVALIDATED
and no Age
header. This happens until this resposne falls out of cache. It occurs randomly across various requests.
Detail:
I have an edge worker that is fetch()
ing content from another site which is using cloudflare. Sometimes, a response from the origin has the header cf-cache-status: REVALIDATED
. What appears to happen is that my edge worker appears to store this header in it's own cached response....Managing tiered caching from edge worker after origin response received
fetch()
to another resource and returning that response. The worker is acting on a domain (incoming request and origin request) using tiered caching. Sometimes I want to NOT cache that response but only AFTER I have fetched it and checked the response content. I do not want to check the response content every time - only when the cache was not present (MISS or EXPIRED).
Let's assume that I currently cannot determine what in the request is responsible for causing this but I sometimes get a bad (status 200 but content contains erroneous elements) response from the origin.. I do not control this origin. My cf
options object passed to fetch()
are cacheEverything: true
and 'cacheTtlByStatus': {'200-299'}: 12345,
so any 200 response will be cached, even if I later detect that it was bad. I can try to detect the erroneous response but how would I stop this response being stored in cache on this occasion so the next call for this resource doesn't respond with the bad response again? My understanding is that the tiered cache is populated based on the response from fetch()
. Is this accurate?...Mongoose Probelm - pls help ;-;
AWS batch jobs
Access to Cloudflare Images
fetch
subrequest is the most flexible way to go. However, it is beyond me how I can access the image given the image id from the worker? Am I supposed to pass it a complete variant URL instead? Is there a way to load the source image by it's ID and apply transformations to it instead?Error 1101 on code surrounded by try/catch