Workers routes - Zone
i got error forbidden on the workers routes page
9 Replies
Known issue, team is aware. It doesn’t block functionality
to add a custom route path for a workers x, using a specific subdomain, is it required that subdomain to have a worker too ?
like i want
to use
my.sub.com/auth
for a worker auth
does the subdomain my.sub.com
need to have a worker?
idk if u get the ideaI’m not sure what you mean
You’d need a Worker on my.sub.com/auth*
If you only want to cover
my.sub.com/auth*
with your Worker, then no, the Worker doesn't need to cover the entirety of my.sub.com
but where should i forward the dns for that subdomain ?
the problem is that if I use the subdomain for a worker, I get the DNS pointed to that worker, but without a worker, I don't know where to point the subdomain DNS record
Is there supposed to be something else on the subdomain?
Or is it just the Worker?
IE, what do you want to happen if you go to
my.sub.com
?okey here is my steps to be more clear
i have domain:
api.domain.io
and a worker worker-auth
for the moment
and i want
api.domain.io/v1/auth
-> worker-auth
i dont have anything yet for t he base
api.domain.io
In that case, if you intent to have something on
api.domain.io
at some point, add a placeholder AAAA 100::
record. Note though that any route on api.domain.io
that isn't api.domain.io/v1/auth
may throw an error.okey
100::
i was looking for then
thanks! still got error when i select a zone 😦
any idea why
Forbidden. (Code: 10007)