workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
âš¡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
DNS
We came over to Cloudflare to give it a go and had the website up and running but we recto give it a miss and go back to our previous hosting updates the records there and the site was live then after about half an hour to an hour we now get this error is anyone able to help me out ?
Cloudflare integration with Workers and Access
I’m relatively new to web dev but it seems like I can generally improve many aspects of my project by working through Cloudflare.
Currently my project is a Java App running in a Docker container on a dedicated server. I’m using Cloudflare tunnel to proxy the traffic through a non standard port and the DNS is also managed by CF. I have around 193GB and growing video, audio, documents, and 3D models that reside on the dedi. I’m looking into moving those to R2 storage. Q1: Do I need to cache these files locally on my machine or can they be streamed directly from R2?
Secondly - my researching also put me across workers and access. From what I understand I can use Workers to handle the Google Auth and return a session token for the site but I’m unsure how to approach this or how I’m supposed to trust the session token or if I’m misunderstanding this. I do know that once I can trust the email and account that’s accessing the site - I’m in a better position to limit who has admin dashboard acccess via reauthenticating them via CF Access, since I trust my own authentication about as much as I would a toddler with a primed nuclear launch button. ...
Cloudflare keep to Revalidated my static files even my origin tell to keep a half-year
I found that many path got Revalidated very frequently and lead to high load on my origin server. I want Cloudflare to cache this files as most as possible but this keep revalidate all day.
I'm on enterprise plan and support center tell me to try purge that path then that work fine, after that every request for this path got HIT.
That's mean I need to purge all of path which faced this problems....
