Wi'd chat to that caller that isn't working
Jit just seems impossible that it isn't a cf thing.. because if I cname foo.example.com to a different domain the request comes through
Jdo you say this because cf wouldn't be applying any firewall in that case?
Wyup
Joh crazy
JI'm literally stumped then. I don't see how the sender of a http request would fail to send that request only if the domain they are sending to ends up going to a cloudflare worker
Jthe fact that it also doesn't work when transparently tunnelled through a netlify site makes me think that cf must not be allowing the request through based on what it looks like, rather than it being a problem with the sender
Jbut I appreciate the fact that I don't control the sender makes it hard to debug
Jhence spending a whole day trying to figure this out 
NI couldn't find a pricing calculator for the standard pricing model, so I created one:
https://standard-model-pricing-calculator.pages.dev/
https://standard-model-pricing-calculator.pages.dev/
J@Walshy tried putting the same code on deno.deploy and forwarding requests to that and it works fine 
WStill doesn't point to cf sadly haha
WWe've seen sites do weird things when going to CF IPs
WI can't think of anything on CF that would prevent it, so if you're sure your code isn't invoked. I'd talk to that sender
Jyeah, I really don't know enough about networking and http to know where a problem could come from
J@Walshy but the fact that the request is going via a netlify rewrite should mean that to the requester it makes no difference where the response ultimately comes from, and it's impossible to tell
Junless I'm misunderstanding how it works
WYes, to the caller they'd see netlify. So, does netlify have any info?
Jnope, another black box, but I've eliminated netlify from the equation because I get the same behaviour if I use cloudflare pages
WAre you able to add headers to the caller?
Jcan't do anything with the caller, just had a look and don't think netlify lets you do anything with headers when rewriting.. what I was thinking of doing was putting a simple function on deno deploy that would forward the request to my worker, then if that doesn't work I'd be able to see what happens
WYeah even having a status code would help a lot
Jok, moment of truth
J@Walshy bingo! It's returning 403
Wok so something is blocking it :Hmm:
Wsend me the pages.dev
Wi need to sleep but i can take a look for 5 mins
Jthankyou!!
Ois generating IDs with nanoid very expensive computationally for workers? some requests taking nearly 400ms of cpu time seems a bit excessive
Olike i was generating at most 40 ids per request which doesn't seem that bad to me
Orunning a benchmark of generating the ID gives me a p999 of
525ns
SHello guys
SI want to detect if the traffic was comming from verified bot , (( if verified bot )) --> do that
Show I can do that with cloudflare worker , I have busniess plan
RI believe it's
request.cf.botManagement.verifiedBot
ADoes
I added
I'm sure my tail worker is called
wrangler.tomlI added
tail_consumers = [{service = "tail"}]I'm sure my tail worker is called
tailtail(event)
ITail workers are quite hard to debug, you can try the dashboard logs and potentially create an endpoint in that tail worker that mocks some of the tail events to test if your worker is doing what you expect to do.
IQuestion in regards to service bindings, reading environment variables and latencies. I've a worker called Edge Config that exposes 2 RPC functions,
It's a Pages -> Workers service binding, both have smart placement turned off. Is this latency normal, how can I further reduce this? Any other recommendations to have dynamic config with close to 0 latency for reads?
setSecretgetSecretsetSecretgetSecret147msIt's a Pages -> Workers service binding, both have smart placement turned off. Is this latency normal, how can I further reduce this? Any other recommendations to have dynamic config with close to 0 latency for reads?
AI added this in the
fetchtailWhat is https://internet-measurement.com/ ? It keeps requesting to my worker on different ports like 8443, 8880 and 2086
Nwell you can read maybe 
AHow do I block them?
Cthere's tons of companies and projects which scan the entire web and ip space, not particularly harmful,espec not to a worker which isn't going to be vuln to anything
Cif you want to try to block those, disable your workers.dev for that worker and use Custom Domains/Routes to bind your worker to your domain, and you can use a rule like
not cf.edge.server_port in {80 443}why 
AMy workers send me a discord message in some cases, it’s a bit annoying to receive messages when I didn’t call them
Nyou will always get some random requests
Sif (request.cf && request.cf.botManagement) {
const verifiedBot = request.cf.botManagement.verifiedBot;
if (verifiedBot) {
return fetch(request);
const verifiedBot = request.cf.botManagement.verifiedBot;
if (verifiedBot) {
return fetch(request);
Sdoes it work like that ??? does it work for busniess plan ???
