From 1f3c63c2326683c91d71e8bcf397f58963e111b3 Mon Sep 17 00:00:00 2001 From: sofietoft Date: Tue, 12 Nov 2024 09:42:31 +0100 Subject: [PATCH] Add note about client side requests --- 14/umbraco-cms/reference/routing/custom-routes.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/14/umbraco-cms/reference/routing/custom-routes.md b/14/umbraco-cms/reference/routing/custom-routes.md index c5c992142ec..717ef8cbfbd 100644 --- a/14/umbraco-cms/reference/routing/custom-routes.md +++ b/14/umbraco-cms/reference/routing/custom-routes.md @@ -42,6 +42,12 @@ For a request to be considered executing in an Umbraco context, and therefore th Don't fret if this all seems a bit overwhelming, we'll be going through an example of the last two options. +{% hint style="info" %} +Is your custom route endpoint considered a **client-side request**? + +[Learn more about how to handle these in the Client-Side Requests section of this article.](#client-side-requests) +{% endhint %} + ### Custom route with IVirtualPageController As mentioned, with this approach we need to implement the `IVirtualPageController` interface, this interface only has one method `FindContent` which accepts an `ActionExecutingContext`: