Is it possible for a worker to call itself via fetch

[christian.s]

I have an odd requirement for my worker to call itself via the fetch api, currently it returns a 403 error. Is this possible? thanks.

[anon9246926]

Service bindings allow a worker send requests to another worker. As far as I am aware, it is not possible for a worker to call itself.

Searching the forums

@harris

For example, consider a worker which just modifies request URL paths, and is deployed on *example.com/*. Should its subrequests go to the origin, or to itself? It may actually have a legitimate recursive design, with a base case that should eventually go to the origin. But how do we know the difference between that base case and the general case?

So if a worker was to call itself, how would it know when to stop calling itself?

Why would you need a worker to call itself in the first place?