Well, for one, anyone with access to your account can just read the API Key
Well, for one, anyone with access to your account can just read the API Key
HFor Secrets, once they are set, they cannot be viewed from the dashboard directly
Ianyone with access to your accountthats just me, right? (i also have 2fa)
HAssuming that you don't invite anyone else to manage parts of your account, nor share an API key for your CF account with anyone else
.Why does a response from a worker sometimes show not secure?
JWhat do you mean? Are you accessing the worker over http, or https?
.Through a route on my domain, yes
JHttp, or https? If you access over http, most browsers show a ‘not secure’ warning nowadays
.Now it isn’t showing not secure, but it was earlier
.https
JThat’s unlikely. If you can reproduce with a https link, please let us know
SHi, i have a question about Workers. If I redirect a request to another domain(my domain but in a different zone) I always get CF_CONNECTING_IP - 2a06:98c0:3600::103 in the header, as I understand this is normal CF behavior. Is there any way I can “bypass” this rule so that I can find out the real IP address of the person making the request?
JYou'll likely want to use the
x-forwarded-for header, or attach your own header that contains the original IPSThanks, I'll try that
MAnyone have Parler-TTS running on CF edge infra?
MParler-TTS is the Hugging Face open source model
MHi, anyone knows about having a static IP on your CF worker ?
Jips are not static but they are dynamic based on data centre location
https://www.cloudflare.com/ips/
here are all listed ip ranegs, you can use them in iptabel of servers, or anywhere to identify requests from cloudflare
https://www.cloudflare.com/ips/
here are all listed ip ranegs, you can use them in iptabel of servers, or anywhere to identify requests from cloudflare
This page is intended to be the definitive source of Cloudflare’s current IP ranges.
MWhich means i can not provide my IP to external third party services by static itself ?
HIf your code is on GitHub you should definitely put it in a secret
HEven if the repo is private
HBesides that it's also just good practice and only takes a few seconds, there's no reason not to do it
AFrom the docs:
That cache is per location, so if you have someone hit your worker from NYC it will then cache for 5 minutes but just in NYC (well, the server closest to NYC let's say), and then if someone hits from London 1 min later, there will be no cache (as it wouldn't hit the NYC cache, excluding some outrageously insane scenario where the entire of Europe is down or something) but then there would be cache in the London DC etc.
At least, that's my understanding and would explain what you are seeing
That cache is per location, so if you have someone hit your worker from NYC it will then cache for 5 minutes but just in NYC (well, the server closest to NYC let's say), and then if someone hits from London 1 min later, there will be no cache (as it wouldn't hit the NYC cache, excluding some outrageously insane scenario where the entire of Europe is down or something) but then there would be cache in the London DC etc.
At least, that's my understanding and would explain what you are seeing
AIt depends really, is 1k reads a day a problem? You get 100k reads for free on the free plan, so is it more a performance thing vs a $$$ thing? As KV will be a little slow and incur high(er) latency if you have to read from a central data store for example (usually a few hundred ms in my experience)
AAnd for now at least, D1 data is held centrally with no read replicas (it's coming). Personally I'd use D1 as it seems more fitting for this kind of use case, where you presumably want to block people indefinitely vs I use KV for caching in high-read situations
HIs there a way to impose a hard limit of 1 actively running request per user id (or any identifier) per location. I'm currently using a simple KV with a bool, but it's not quite fast enough if you make two requests at the same time. Would a queue be a good fit for this or is there a simpler solution?
CYou should look at durable objects
HAhhhh yeah that makes sense, thank you!
GFor only one account we have in cloudflare and all domians are working fine yesterday, today after enable the 2FA dashboard not showing domains . after that revoking 2FA but still same issue help ASAP...
Cis it needed/worth adding queues to my worker when jobs are triggerd from page functions? or if i have a Service binding to the worker from my page projects will it always work.. ?
AService Bindings are a zero-cost abstraction, so while “always work” is probably never going to the case for anything in software engineering, imo it is reliable enough where you can assume it’s going to work - typically the call in the secondary worker happens in the same thread on the same Cloudflare server as the calling worker, so there’s no networking etc. - up to you to decide for your use case, and more info at https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/
Calright, sounds good. thanks for the insight!
AI haven’t looked at the repo, but is this as part of an API call, or a user interaction on a website? If it’s the former, is there a reason to use the queue rather than just process it in the worker directly? If it’s a website where the user enters the URL, you can have the first backend call put the URL in the queue, and then have the frontend poll a separate endpoint to see if the result is in KV, as an option. You can also do the same approach if it’s an API to be honest: have a POST request to create jobs, then a separate GET request to see if the job has completed (or offer a webhook that sends the response when it’s ready). Really depends on your use case.
APeeked at the repo - it's sort of what it does. You can see that there is the endpoint to add to the queue in https://github.com/cloudflare/queues-web-crawler/blob/master/pages/functions/requestToCrawlSite.js and then it gives a link to a URL that is handled by https://github.com/cloudflare/queues-web-crawler/blob/master/pages/functions/page/%5Burl%5D.js to show the results
Ahttps://developers.cloudflare.com/workers/wrangler/environments/
Can booth the dev and production worker have the same name and live undertneath one service in cloudflare, but use different routes that is defined underneath the worker
Can booth the dev and production worker have the same name and live undertneath one service in cloudflare, but use different routes that is defined underneath the worker
Cloudflare Docs
Deploy the same Worker application with different configuration for each environment.
AIt's in the docs you linked:
So no, they cannot have the same name - you can map multiple routes to a single environment, but you can't have dev/production with the same name but different bindings etc.
So no, they cannot have the same name - you can map multiple routes to a single environment, but you can't have dev/production with the same name but different bindings etc.
AYea that makes sense I was just making sure
AHave you tried using a Durable Object instead of a queue? See: https://developers.cloudflare.com/browser-rendering/get-started/browser-rendering-with-do/ it should allow you to achieve the same outcome but a DO is more suited to a synchronous workflow
Cloudflare Docs
By following this guide, you will create a Worker that uses the Browser Rendering API along with Durable Objects to take screenshots from web pages and store them in R2.
Lfor load context, is that something you should stuff things like auth, db, session management tools into?
SIs this per HTTP request or 30s across all HTTP requests?
APer HTTP request (https://developers.cloudflare.com/workers/platform/limits/#worker-limits for full details) and everyone is on the Standard pricing model now
MCan enterprise users have static ip ?
HPer request
WCloudflare Docs
Cloudflare Aegis provides dedicated egress IPs (from Cloudflare to your origin) for your layer 7 WAF and CDN services. The egress IPs are reserved exclusively for your account so that you can increase your origin security by only allowing traffic from a small list of IP addresses.
