Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Document behavior and limits of calling fetch() to another Worker #858

Closed
ispivey opened this issue Jun 1, 2020 · 0 comments
Closed

Document behavior and limits of calling fetch() to another Worker #858

ispivey opened this issue Jun 1, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@ispivey
Copy link
Contributor

ispivey commented Jun 1, 2020

I couldn't find this in the docs currently.

We should document the behavior and limitations of making a fetch() call to a URL that matches a route that runs a Worker.

If the fetch URL is on the same zone as the original request, the request will go to the origin, and will not be handled by any other Worker.
If the fetch URL is on a different zone, the request will be handled by the Worker matching the route.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants