Skip to content

Commit 0db7976

Browse files
committed
Fix more links
1 parent 6c5d0fb commit 0db7976

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

src/content/docs/workers/static-assets/routing/worker-script.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ sidebar:
88

99
import { WranglerConfig, TypeScriptExample, Aside } from "~/components";
1010

11-
If you have both static assets and a Worker script configured, Cloudflare will first attempt to serve static assets if one matches the incoming request. You can read more about how we match assets in the [HTML handling docs](/workers/static-assets/routing/html-handling/).
11+
If you have both static assets and a Worker script configured, Cloudflare will first attempt to serve static assets if one matches the incoming request. You can read more about how we match assets in the [HTML handling docs](/workers/static-assets/routing/advanced/html-handling/).
1212

1313
If an appropriate static asset if not found, Cloudflare will invoke your Worker script.
1414

15-
This allows you to easily combine together these two features to create powerful applications (e.g. a [full-stack application](/workers/static-assets/routing/full-stack-application/), or a [Single Page Application (SPA)](/workers/static-assets/routing/single-page-application/) or [Static Site Generation (SSG) application](/workers/static-assets/routing/server-side-generated/) with an API).
15+
This allows you to easily combine together these two features to create powerful applications (e.g. a [full-stack application](/workers/static-assets/routing/full-stack-application/), or a [Single Page Application (SPA)](/workers/static-assets/routing/single-page-application/) or [Static Site Generation (SSG) application](/workers/static-assets/routing/static-site-generation/) with an API).
1616

1717
## Run your Worker script first
1818

src/content/docs/workers/vite-plugin/tutorial.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ assets = { not_found_handling = "single-page-application" }
6868

6969
</WranglerConfig>
7070

71-
The [`not_found_handling`](/workers/single-page-application/) value has been set to `single-page-application`.
71+
The [`not_found_handling`](/workers/static-assets/routing/single-page-application/) value has been set to `single-page-application`.
7272
This means that all not found requests will serve the `index.html` file.
7373
With the Cloudflare plugin, the `assets` routing configuration is used in place of Vite's default behavior.
7474
This ensures that your application's [routing configuration](/workers/static-assets/routing/) works the same way while developing as it does when deployed to production.

src/content/partials/workers/static_asset_routing_reference.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,4 +61,4 @@ In most cases, configuring `assets.not_found_handling` to <code>{props.not_found
6161

6262
Requests are only billable if a Worker script is invoked. From there, it is possible to serve assets using the assets binding (depicted as the dotted line in the diagram above).
6363

64-
{props.not_found_handling === "single-page-application" ? "Although unlikely to impact how a SPA is served, you" : "You"} can read more about how we match assets in the [HTML handling docs](/workers/static-assets/routing/html-handling/).
64+
{props.not_found_handling === "single-page-application" ? "Although unlikely to impact how a SPA is served, you" : "You"} can read more about how we match assets in the [HTML handling docs](/workers/static-assets/routing/advanced/html-handling/).

0 commit comments

Comments
 (0)