Wlol i think its cheap
Wanyways thanks!!
Cway cheaper then it was at one point yea, and if you get to a really large point you could get even potentially cheaper ent pricing like shopify and such
LGot it, thank you
Wooo nice, hope i do 
Wso basically the users can add my fallback origin to their dns
Wwith this workers function
Wand it will consume my worker requests right?
Cyes, although a point worth mentioning is you have to add them as a custom hostname (in dash or via api) first, and then they cname (or do the prevalidation first to avoid downtime) and get activated
Wye basically give them my the option to use my cname and if they want they can just validate their own
Wbut
Wi think for my app it would be better to do prevalidation first
Wlike on boarding
SHi everyone,
I'm currently working on adding a custom domain feature to my project, and I could use some assistance. Here are the details of my setup:
I have an Angular site hosted on Cloudflare Pages with the following DNS settings for my domain (site.com):
I have enabled Cloudflare for SaaS and added "fallback.site.com" as the fallback origin for site.com.
I also have a domain (test.com) and have created a custom hostname (app.test.com). I generated a TXT validation and added the TXT record and a CNAME record (CNAME --- app --- cd.site.com) to the test.com DNS records.
Additionally, I have a worker that routes requests coming to site.com. The worker acts as a reverse proxy, serving content from either the Pages site or a WordPress site, while keeping the URL in the browser as site.com/*. However, when I try to handle the custom domain and serve a page from site.com/custom-domain, the URL in the browser changes from app.test.com to site.com/custom-domain.
Here I have attached index.js and wrangler.toml:
And here is the wrangler.toml configuration:
How can I ensure that the content of the pages is loaded while keeping the URL the same in the browser(app.test.com)? Any help or guidance would be greatly appreciated!
Thanks in advance for your help!
I'm currently working on adding a custom domain feature to my project, and I could use some assistance. Here are the details of my setup:
I have an Angular site hosted on Cloudflare Pages with the following DNS settings for my domain (site.com):
I have enabled Cloudflare for SaaS and added "fallback.site.com" as the fallback origin for site.com.
I also have a domain (test.com) and have created a custom hostname (app.test.com). I generated a TXT validation and added the TXT record and a CNAME record (CNAME --- app --- cd.site.com) to the test.com DNS records.
Additionally, I have a worker that routes requests coming to site.com. The worker acts as a reverse proxy, serving content from either the Pages site or a WordPress site, while keeping the URL in the browser as site.com/*. However, when I try to handle the custom domain and serve a page from site.com/custom-domain, the URL in the browser changes from app.test.com to site.com/custom-domain.
Here I have attached index.js and wrangler.toml:
And here is the wrangler.toml configuration:
How can I ensure that the content of the pages is loaded while keeping the URL the same in the browser(app.test.com)? Any help or guidance would be greatly appreciated!
Thanks in advance for your help!
index.txt2.34KB
wrangler.txt359B
NMy Cloudflare Worker is blocking fetch requests originating from Vercel or Netlify. How can I stop this?
Dcan a tail worker be the same codebase as the original worker? like is it possible to just call the same workers fetch handler? I don't want to stand up a new worker right now and hoping to kinda hack it.
Also do they get triggered in local dev with wrangler?
Also do they get triggered in local dev with wrangler?
Ddoesnt seem to be working, but im not quite sure how to tell honestly. Tailing the logs I dont see the tail worker called, but not sure if that would actually show.
Banyone got
pino.transportnevermind; after battling it for an hour or so, i've decided to write a little wrapper around
console.log
CIs there an easy way to tell if the worker is being served from wrangler dev? I have a use case where I want to know if the worker is actually deployed to allow/disallow localhost in CORS. Right now I'm using the CF-Ray header to detect this, but it doesn't work if the wrangler dev is using a remote deployment
CYou should check your WAF logs. Probably where the request is being blocked.
DIirc the cf object will only be present if served from CloudFlare. https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties
HIt’s also present in local dev
Tno but i cannot get kafka to work either
DOops, never mind.
SThis basically means that smart placement is slower than the normal placement, or am I wrong? D1 database is hosted in East US and my service that's fetching data from this worker every minute is also located in the East of the US.
CIf you have a D1 DB attached and you turn on Smart Placement, it overrides its location to be closest to the D1 DB, and D1 Requests aren't going to show up in any of the Request Duration/Subrequest charts I don't think
TIf I want to guard my api with a bearer token, is it better to use the cloudflare access or do the check in my middleware?
I was reading that cache api doesn't work behind cloudflare access, any other downsides? what about performance?
I was reading that cache api doesn't work behind cloudflare access, any other downsides? what about performance?
CYou can check there is an API token with WAF rules and check the validity of the token in your middleware
Jumm, is it normal for
performance.now()I feel like it should never return 0..
Jseeing as performance.timeOrigin = 0
Cit only advances on i/o: https://developers.cloudflare.com/workers/runtime-apis/performance/
(and the timeOrigin in Workers is 0 as described in there as well)
(and the timeOrigin in Workers is 0 as described in there as well)
Cloudflare Docs
Measure timing, performance, and timing of subrequests and other operations.
JBut shouldn't it still be initialised with a sensible time?
JIt breaks Effect's clock implementation because it tries to calculate the origin based on performance.now() at initialisation
Cthere's some comments in workerd about it: https://github.com/cloudflare/workerd/blob/882c33f4ce989cd140da00695cd75f066558fc41/src/workerd/api/global-scope.h#L86C1-L86C8
JAnd then suddenly time jumps forwards by half a century
JThe thing is it doesn't behave like Date.now().. date doesn't return zero at initialisation
JHow do you get to the in bowser quick editor for a worker in the dashboard?
Coh you mean outside of a request it now() returns 0?
JYes
Cit's just calling dateNow which if not in an IoContext/Request does that: https://github.com/cloudflare/workerd/blob/882c33f4ce989cd140da00695cd75f066558fc41/src/workerd/api/util.c%2B%2B#L210
JOh, so Date.now() behaves the same?
CI guess otherwise they'd need to track when the isolate spun up and then set another variable for unscoped requests
Cit should, let's find out!
Ctop right
Chmm yea
Cdid they hide it again? what the heck