You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/aegis/configuration-options/workers.mdx
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,13 @@ head:
9
9
10
10
[Workers](/workers/) provides a serverless execution environment for you to create applications leveraging Cloudflare's global network.
11
11
12
-
When paired with Aegis, whenever Cloudflare's developer platform needs to access services on your origin, it will use the dedicated IP addresses.
12
+
Refer to the sections below for information on how Aegis pair up with Workers.
13
13
14
14
## `fetch`
15
15
16
-
For Workers subrequests — meaning requests from one Worker to another — it is expected that different IPs are used. However, [`fetch()` requests](/workers/runtime-apis/fetch/) to external origins made by a Worker invoked via a subrequest will use the dedicated IP addresses.
16
+
[`fetch()` requests](/workers/runtime-apis/fetch/) to access services on your origin will use Aegis IP addresses.
17
+
18
+
For Workers subrequests — meaning requests from one Worker to another — it is expected that different IPs are used. However, [`fetch()` requests](/workers/runtime-apis/fetch/) to external origins made by a Worker invoked via a subrequest will use Aegis IP addresses.
0 commit comments