Merge branch 'production' into kian/PCX-16226

Author: kodster28

package-lock.json

@@ -36,7 +36,7 @@
 		"@astrojs/starlight-docsearch": "0.6.0",
 		"@astrojs/starlight-tailwind": "4.0.1",
 		"@cloudflare/vitest-pool-workers": "0.8.32",
-		"@cloudflare/workers-types": "4.20250522.0",
+		"@cloudflare/workers-types": "4.20250529.0",
 		"@codingheads/sticky-header": "1.0.2",
 		"@expressive-code/plugin-collapsible-sections": "0.41.2",
 		"@floating-ui/react": "0.27.8",
@@ -71,7 +71,7 @@
 		"fast-glob": "3.3.3",
 		"fast-xml-parser": "5.2.3",
 		"github-slugger": "2.0.0",
-		"globals": "16.1.0",
+		"globals": "16.2.0",
 		"hast-util-heading-rank": "3.0.0",
 		"hast-util-select": "6.0.4",
 		"hastscript": "9.0.1",

package.json

@@ -711,6 +711,7 @@
 /fundamentals/setup/account/customize-account/appearance/ /fundamentals/account/customize-account/ 301
 /fundamentals/setup/account/customize-account/communication-preference/ /fundamentals/account/customize-account/ 301
 /fundamentals/setup/account/customize-account/language-preference/ /fundamentals/account/customize-account/ 301
+
 /fundamentals/setup/account/* /fundamentals/account/:splat 301
 /fundamentals/setup/manage-domains/* /fundamentals//manage-domains/:splat 301
 /fundamentals/setup/manage-members/* /fundamentals/manage-members/:splat 301

public/__redirects

@@ -64,7 +64,7 @@ curl -X POST https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/comp
 
 ### Universal provider
 
-You can also use this pattern with a [Universal Endpoint](/ai-gateway/universal/).
+You can also use this pattern with the [Universal Endpoint](/ai-gateway/universal/) to add [fallbacks](/ai-gateway/configuration/fallbacks/) across multiple providers. When used in combination, every request will return the same standardized format, whether from the primary or fallback model. This behavior means that you do not have to add extra parsing logic to your app. 
 
 ```ts title="index.ts"
 export interface Env {

src/content/docs/ai-gateway/chat-completion.mdx

@@ -57,6 +57,10 @@ netsh int ipv6 set dynamicport udp start=11000 num=50000
 
 </TabItem> </Tabs>
 
+### Private DNS
+
+DNS queries utilize [more system resources](#estimated-throughput) compared to TCP and non-DNS UDP requests. To optimize service availability, Cloudflare recommends splitting [private DNS traffic](/cloudflare-one/connections/connect-networks/private-net/cloudflared/private-dns/) into its own Cloudflare Tunnel. The tunnel should run on a dedicated host and only include routes for your internal DNS resolver IPs.
+
 ### ulimits
 
 On Linux and macOS, `ulimit` settings determine the system resources available to a logged-in user. We recommend configuring the following ulimits on the `cloudflared` server:

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/system-requirements.mdx

@@ -48,15 +48,7 @@ Configuration files that contain ingress rules must always include a catch-all r
 
 ### How traffic is matched
 
-When `cloudflared` receives an incoming request, it evaluates each ingress rule from top to bottom to find which rule matches the request. Rules can match either the hostname or path of an incoming request, or both.
-
-:::note[Wildcards]
-
-You can use wildcards to match traffic to multiple subdomains or paths. For example, if you set the `hostname` key to `*.example.com`, both `test.example.com` and `try.example.com` will route traffic to your origin.
-
-:::
-
-If a rule does not specify a hostname, all hostnames will be matched. If a rule does not specify a path, all paths will be matched.
+When `cloudflared` receives an incoming request, it evaluates each ingress rule from top to bottom to find which rule matches the request. Rules can match either the hostname or path of an incoming request, or both. If a rule does not specify a hostname, all hostnames will be matched. If a rule does not specify a path, all paths will be matched.
 
 The last ingress rule must be a catch-all rule that matches all traffic.
 
@@ -81,6 +73,12 @@ ingress:
   - service: https://localhost:8003
 ```
 
+#### Wildcards
+
+You can use wildcards to match traffic to multiple subdomains. For example, if you set the `hostname` key to `*.example.com`, both `alpha.example.com` and `beta.example.com` will route traffic to your origin. `cloudflared` does not support wildcards in the middle of the hostname, such as `test.*.example.com`.
+
+You can also enter regular expressions for the `path` key. For example, if `hostname` is `static.example.com` and `path` is `\.(jpg|png|css|js)$`, matching URLs could include `https://static.example.com/data.js`, `http://static.example.com/images/photo.jpg`, and so on. Cloudflare parses the path regex using the [Go `syntax` package](https://pkg.go.dev/regexp/syntax).
+
 ### Supported protocols
 
 In addition to HTTP, `cloudflared` supports protocols like SSH, RDP, arbitrary TCP services, and Unix sockets. You can also route traffic to the built-in `Hello World` test server or respond to traffic with an HTTP status.

src/content/docs/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file.mdx

@@ -1,8 +1,6 @@
 ---
 type: example
 summary: Access the name from within a Durable Object using RpcTarget.
-tags:
-  - Durable Objects
 pcx_content_type: example
 title: Use RpcTarget class to handle Durable Object metadata
 sidebar: