Well its more of env var behavior not secrets
Well its more of env var behavior not secrets

req.cf would indicate the location of the where the request came from, not where it was served fromloc seems quite useful tooreq.cf.locationreq.cf value is set in the first Worker in the chain. It isn't modified if you pass the request on to another Worker(via Service Bindings) or a Durable Objectcdn-cgi/trace shows my colo is FRA (France), OpenAI is still rejecting my requests when I connect via a VPN to Hong KongFRA is Frankfurt in Germany. But also, iirc, requests from Workers still pass along a connecting IP header, and I'm wondering if that also happens for the DOfetch requests from a DO might include, without my explicit configuration, a header indicating the IP the incoming request originated from?



Share some remote service tokens, or that same service address for example.
...but your local DB address/password is your own setup

secrets storereq.cfreq.cfcolo=req.cf.locationcdn-cgi/traceFRAFRA 'cf-ipcountry': 'HK',secrets store((await (await fetch("https://www.cloudflare.com/cdn-cgi/trace")).text()).match(/^colo=(.+)/m) as string[])[1]