> Changes may take up to 60 seconds to be visible when reading key-value pairs. I guess maybe i'm thinking of this, but I guess that's probably not actually a cache, but instead just replicating changes to other datacenters

Are your workers simple retrieving static content to serve up? Might it make more sense to store such static assets in a repo and use #789155108529111069 to serve them directly via our cache?

using a worker for a simple proxy, and after a few requests all of the responses from

fetch

come back as error 1015! any ideas?

Hello! Are you running a load test? The 1015 error means a client IP is being rate-limited - which is an anti-abuse measure in our network.

no i dont think so!

I'm trying to set up wrangler tail right now, but i'm having trouble

i'm not sure what to put in the wrangler.toml file if I want to connect to an existing worker

but there aren't any logs!

Let me message you to look deeper into your wrangler.toml file. Usually when configuring, this link to the docs helps: https://developers.cloudflare.com/workers/cli-wrangler/configuration#example

No static assets. I use Workers to generate identicons. See: https://avatars.dicebear.com Docs: https://avatars.dicebear.com/docs/http-api

You could ditch "serverless" and still benefit from cloudflare edge. Run a server in NodeJS and Express that generates the asset, and use Cloudflare as a Proxy with no Workers. If the identicons are not security critical, why not generate on the client browser?

Cloudflare Workers are faster and cheaper than a solution via a NodeJS server. The avatars can also be generated client-side. The HTTP API exists for a quick start. I also just wanted to describe my workaround here. It is not a problem to solve for me.

I was actually wondering why are you using different CDN on top of Workers, now its clear 🙂

anyone used this? https://github.com/berstend/tiny-request-router

considering rebuilding lilredirector 1.0 with it

I use this router.

Yeah, I've used it and it's nice.

Using it aswell - good library 🙂

hey all - i'm working on a new page for our docs for videos about workers. anyone have anything they've watched around workers they think should be on there?

Some people hitting my worker API are saying that they're getting a cloudflare captcha, is there a way I can force that to be turned off?

On the dashboard > zone > page rules. Then create a rule, for security level: essentially off

I had browser integrity check off

Okay, Will see how this helps

This is my new favorite discord server haha

🎉 https://blog.cloudflare.com/meet-the-workers-team-over-discord/

Glad to see that Cloudflare finally has a official Discord server 😄

👋

Hello 👋, happy to be here 💙

Exciting seeing companies do something like this, would be interesting to have similar Servers, like for Netlify, AWS etc.