hang on, isn't this pointless since I already log the request headers in my Worker?
hang on, isn't this pointless since I already log the request headers in my Worker?
C
Doh derp
Dis there any situation where it could change or be helpful?
DI'll remove it for now
Deasier to parse without concat'ing, as I'd be worried that that field might be missing.
DI think it's just parsing that I was worried about
Dis there a way to pad http.request.timestamp.msec to include the the first two leading zeros?
Dyeah
DI feel like I got annoyed when I thought of this last time lol
Dehhhhhhhhhhhhhh
DI know we have some Workers that already use
timestamp-msec-only
BGoogle reCAPTCHA no longer provides 1 million free assessments.
Turnstile time.
Turnstile time.
Uthat is until u hit over 1m and recaptcha is cheaper 
is interesting though very large downgrade in the free
is interesting though very large downgrade in the freeBJokes on you, I'd never hit that! 
BAnd yea, that was my only reason for using it))
UI guess actually if u use managed mode turnstile is unlimited free forgot they did that
Byeah, was just about to say that! i also remembered them being free & unlimited so I checked
Bcloudflare is awesome
UCan still use other modes limited at 1 million I think but I assume managed mode is fine for 99% of people so 
Dah,
client_port0
Dwhat's wrong with managed mode? Can't you sorta use it like non-interactive if you really want to anyway?
UI assume managed mode is fine for 99% of people so
Dyeah but even if it isn't, can't you just put a managed in an offscreen area of the screen, and then use the callbacks?
II have a very simple worker that takes in a url, fetches it, adds a 5 second TTL, and then returns a response. when I spam refresh in my browser, I only get 1 request to the origin per 5 seconds (correct). when I do the same request spam using curl, multiple origin hits happen. anybody know what's going on?
UCache is per datacenter and your browser will stick generally to 1 datacenter (though it can switch) and curl will not. A single colo can also have multiple datacenters. So just because you only hit "DFW" doesnt mean you will hit the same cache.
Ihuh interesting. that makes sense, but wouldn't copying the browser request as curl be as close to a 1:1 as possible?
Iis there a magic incantation to add to the curl request to mimic the browser behavior?
II feel like the hit ratio would be really low if you consider the curl path to be the more common use case (i.e multiple browsers in the same geographical region), no?
II would expect 10 people in the same building to have 1 miss and 9 hits, but it seems like that wouldn't really be the case here?
DIf there’s two nearby PoPs, you would have 2 misses and 8 hits probably.
You may want to enable tiered cache if you’re hoping to reduce requests to the same origin.
You may want to enable tiered cache if you’re hoping to reduce requests to the same origin.
Iooh interesting. that can't happen at the worker level, right?
Dyou enable it on your dashboard. https://developers.cloudflare.com/cache/how-to/tiered-cache/
The When you do your
I don't think a Worker can force in or out of tiered caching (it can only force in or out of caching entirely).
The
fetchfetchI don't think a Worker can force in or out of tiered caching (it can only force in or out of caching entirely).
Tiered Cache uses the size of Cloudflare’s network to reduce requests to customer origins by dramatically increasing cache hit ratios. With data …
Ithank you!
DWe use tiered caching on Worker subrequests to Backblaze B2; saves a ton in terms of latency and cost.
Ibut you have to have that enabled at the "website" level first, right?
Iit's not a worker-level config?
CI never messed with workers/pages yet, almost curious how they could help with a broadcasting service like Discord, Zoom, etc.
DIty!
Dyou will also need to have the Worker listening on a route (or custom domain) for the same domain that you have tiered caching enabled
Di.e. not workers.dev
CWhat are you guys using workers for that substantially helped you? I mean for people with more than 20K unique users daily.
Dwe have less users than that and Workers are still insanely useful.
CI'm kicking around 4K unique daily, only about 1% CPU on the main single core HTTPS server ( I run many services though as users navigate)
CBeen eyeing some of the CF toys you feel?
De.g. what I was working on today is our Worker that acts like a middleware for Azure AI Document Intelligence. The Worker fixes a lot of annoyances/missing features, like storing of results and caching.
CHmm more detail? Unsure of azure AI stuff.
Dit's Microsoft's OCR solution
CI'm mostly running many-to-many broadcasting services like Zoom/etc conferencing stuff.
Coh okay
