Now that we have descriptions on DNS records I just add a description to the Worker record and use r
Now that we have descriptions on DNS records I just add a description to the Worker record and use routes 
KIt did indeed work. Thanks for the hint!
KNot the best solution but the only possible right now. But having it disabled for the whole zone... suboptimal
Ctotal tls certs don't count
Cconvince your upstream to move on from 2006 and support ipv6 
Dahhh
KThey haven't updated their software in the last 4 years but we sadly have to integrate it into our app
KI wish they would do it, but I doubt it
Disn't that ent-only? or am I thinking about tags?
CNeither are Ent-only
CComments are on free, Tags are Pro or higher
Dooo nice! thanks
JHi CF developers. I have an existing worker, and I cannot figure out how to have a 'staging' version and a 'production' version of the same worker. I have tried running
npx wrangler deploy --env production and npx wrangler deploy --env staging but all it does it create a new worker with -production or -staging at the end.JCan someone point me in the right direction?
Cbut all it does it create a new worker with -production or -staging at the end.That is how environments work right now with Wrangler
JI have other workers that in the dashboard are named the same, and they have a dropdown on the worker page where I can select environment
CThere is bits and pieces in the dashboard about the old Service Environments system if you're being confused by that, that shows production and such. James has a write up explaining that all here: https://community.cloudflare.com/t/environments-vs-deployments/451036/2?u=chaika
CThe TLDR being the Wrangler way with entirely different Workers is the best way right now and the intended way. You can have specific settings in your wrangler.toml for specific environments as well https://developers.cloudflare.com/workers/wrangler/environments/
Deploy the same Worker application with different configuration for each environment.
JSo that functionality has been removed? (having the same worker have multiple environments).
CEssentially, iirc it never fully worked anyway
Cthere's just bits of pieces of it left over
UI dont even think it existed for more than a month tbh 
JI have clients that have that functionality currently in their dashboard working.. but ok, thanks for the information!
JI appreciate you taking the time
CI think if they created them before they didn't get taken away, but I imagine the functionality is still half baked/broken/etc
CI don't have any to test with though
FWhat is the best way to debug a 1101 Error and tail says Error: The script will never return a response. For context we are hosting an astro site with SSR as a "sandbox" environment for customers to test CMS changes before deploying (the final page is static). But for some "some minutes - minutes could also last for 20-25 minutes" the page works perfeclty fine and then for a long time there is the 1101 Error and I really cant find a way to debug, etc. Any help / direction would be really appreciated.
AHello
Is anyone using OpenTelemetry in workers (for prometheus format)?
I find it really confusing to just expose some prometheus metrics: MeterProvider, views, MetricReader, etc all the naming and docs are confusing
Is anyone using OpenTelemetry in workers (for prometheus format)?
@opentelemetry/api, @opentelemetry/sdk-metrics, @opentelemetry/exporter-prometheus and co?I find it really confusing to just expose some prometheus metrics: MeterProvider, views, MetricReader, etc all the naming and docs are confusing
KThe Workers ran by DevProd (the team behind Wrangler) use promjs
K
Ayou mean this one? https://github.com/weaveworks/promjs it is deprecated
https://github.com/siimon/prom-client was so much simpler, but I wanted to give a try to otel to do kind of the same
https://github.com/siimon/prom-client was so much simpler, but I wanted to give a try to otel to do kind of the same
AI guess there is no shortcut to just experiment a lot 
no blog post/github code already ready to go ^^
no blog post/github code already ready to go ^^
L
need help
KThe API docs for that endpoint are just bad
LThank you. I will go and try it out right away.
Dhas anyone created a lib to parse xml in cf workers? i'm not familiar with HTMLRewriter and I don't feel like spending a few hours trying to figure it out so I can parse XML data.
KKDoesn't need to be Workers specific
Uok how do you have negative requests per second though
Uoh nvm
Uim sorry what language now
Uim guessing it just auto returns false tho? lol
SThank you Erisa, I'll give it a shot!
MHey!
With
I can access it from the computer on which I started wrangler, but not from my phone... (i can access other ports, if I run a simple web server for example)
I tried upgrading/downgrading wrangler version, nothing changed.
Am I missing something?
With
wrangler dev --ip 0.0.0.0 I used to be able to access http://192.168.1.26:8787/ from my phone connected to the same wifi network. I can access it from the computer on which I started wrangler, but not from my phone... (i can access other ports, if I run a simple web server for example)
I tried upgrading/downgrading wrangler version, nothing changed.
Am I missing something?
ZFor example if I host an api for storage or whatever and someone abuses it will I be held liable or he
ZCuz I don’t want neither a ban from cloudflare nor a legal problem
ZI will respond of course
Syeah use regex. we do this in prod for sitemap parsing and it works flawlessly despite the fact people will reply to this saying you should never do it 
Dpretty sure we use HTMLRewriter for parsing XML somewhere in our company
