Maybe try #🦀rust-on-workers
Maybe try #
rust-on-workers
rust-on-workers
COoo ok! Will do!
SI'm getting a 522 when calling my Worker via its public custom domain from inside the same Worker, any ideas?
Sits a blank route that just returns a 200. I can call it fine locally
UNot surprising lots of issues with that I'd use service bindings
Cor you could try seting the no miminal subrequests compat flag https://github.com/cloudflare/workerd/issues/787#issuecomment-1597396851
GitHub
Which Cloudflare product(s) does this pertain to? Workers/Other What version of Wrangler are you using? 2.9.0 What operating system are you using? Mac Describe the Bug Same zone worker <-> wo...
Swhy not surprising? it is just like calling any other API right?
SI'm using it to proxy webhook requests to the correct environment
Sservice bindings not gonna work for this use case
Cno, worker to worker is very special lol
Cyou can't do same zone worker to worker with routes
Sbut I actually do it already somewhere else
Salthough I guess that is technically in a DO
UService bindings are actually a perfect use case for proxying to the correct env 
why would it not work for you?
why would it not work for you?Sughh this is a big mess
CWorker to worker same-zone over routes > no
Worker to worker same-zone over Custom Domains -> should work, with compat flag?
Worker to worker different zones -> should work, will use worker ipv6
Worker to worker service bindings -> works and optimal, request doesn't go over network, fast
Worker to worker same-zone over Custom Domains -> should work, with compat flag?
Worker to worker different zones -> should work, will use worker ipv6
Worker to worker service bindings -> works and optimal, request doesn't go over network, fast
Sdid not expect this to not work
Sdoes that flag actually work?
UI'd personally suggest never calling your own worker with an outbound fetch and always using service bindings personally. Works the best and always
Syeah, I understand
SI don't need to code the extra logic of checking if the current worker is calling the same worker and then figuring out the binding when it should just work as is
Cwell my understanding is some of that complexity is needed because Workers can runs on routes and call the origin behind them
Cwouldn't want to infinite loop
Ccustom domains were supposed to have the ability to act as a real origin and just work, and they did for a bit, but then got broken with the minimal subrequest stuff, so need compat flag
Sthought I'd be making it easy on myself by putting this proxy in the worker instead of in a Supabase edge function, I guess I messed up
Sno_minimal_subrequests did not seem to workSbtw it works locally, of course. so did not spot the issue until now
Smaybe I should proxy it through a DO 
Ahey, i have a quick question regarding billing
im piping files from Backblaze B2 through CF Workers and have a simple hono app that grabs files and sends them to the user
will the time it takes for this file to go to the user be counted under CPU time?
im piping files from Backblaze B2 through CF Workers and have a simple hono app that grabs files and sends them to the user
will the time it takes for this file to go to the user be counted under CPU time?
JHi, Do Workers use CDN when serving data from R2 storage ? or can it be configured to use a CDN ?
UIf by CDN you are asking mostly about cache then you can use the Cache API in workers. Or you can use an R2 public domain instead which will directly connect to the CDN assuming all files being public is fine.
VHey, is it possible to create a trigger for a worker that only runs on URL-s with page queries ( like this ?=page1 ). Inside this route field?
V
VI tried setting route to domain/*, and creating regex inside worker that matches the query. I think this is not the best way to do it since the worker always checks whole domain
KUnfortunately not.
Vwhat do you think about my solution then. I think there will be too many requests, but i neeed to somehow target URLS with page queries. I cant to seem find a better way
KThere is no better way currently - routes don’t support having query params in them
IHey please help me I’m unable to access the login page of Wordpress site but my site is accessible I don’t know why it’s not working when i pause the cloudflare dns then it’s working when resumed cloud flare DNS then again not opening the login page of wordpress dashboard please help mcqs.io/wp-admin
I
IIt’s saying clear the cache did it still not working as well as tried on other devices?
LWorkers page do not work, why ?
Lbasicaly all this pages not work
L
Lbtw. I logged out, clear cookies but no help
AExperiencing the same!
BWe are currently unable to deploy worker from CLI
✘ [ERROR] Received a malformed response from the API
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if I... (length = 6434)
Edit:
Now it is currently resolved.
✘ [ERROR] Received a malformed response from the API
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if I... (length = 6434)
Edit:
Now it is currently resolved.
Sit tells you the problem directly in your screenshot: too many redirects
IPlease tell me the solution what should i do now?
Sare you using Workers?
INo I’m using name.com wordpress hosting and domain purchased from cloudflare im not that too much technical
Sgreat, so please don't use this channel and spam your question
