Redirects in XbyK?

There are several ways to handle redirects, depending on what you are trying to redirect and who you want to manage them (or if you want them managed).

Large number of redirects

These options assume that the redirects are pre-defined and not actively managed by administrators or marketers.

If you have a very large set of pages that need redirected and the only infrastructure you have is the ASP.NET Core app running Xperience, you could use ASP.NET Core's built-in URL Rewriting middleware. This lets you define a configuration file which is loaded at startup and it catches all requests for those URLs which should be redirected and handles them before they ever make it to the rest of your app.

You'd only be able to handle redirects that your ASP.NET Core app received so any old domains would also need to be pointed at your Xperience application, wherever it's hosted.

Xperience has a Former URLs feature which redirects old URLs to new ones. This feature doesn't currently allow for administrators to manage redirects but you could load a bunch of redirects programmatically and rely on Xperience to send old URLs to existing pages in various website channels.

You could also use a load balancer or proxy that sits in front of your ASP.NET Core app. This type of infrastructure typically has a way to load in redirects or traffic rules that it should handle. This offloads the redirect logic to another application which means your Xperience app can focus on DXP-stuff 😅.

Azure Front Door and Cloudflare are popular cloud solutions for this scenario (Kentico's SaaS offering for Xperience by Kentico uses Cloudflare).

You could also self-host something like Yarp or a container running some other web server technology.

Small number of redirects, actively managed

If you have fewer redirects and they need to managed by administrators or marketers you can customize Xperience's administration with a new Application that lets users manage custom redirects. These redirects would be used by ASP.NET Core in a custom middleware. This would be similar to the URL Rewriting middleware option above but the redirects could be dynamically managed from a UI.

If you are interested in this option, check out Michael Eustace's Xperience Community: URL Redirects integration on our Integrations list.

This approach doesn't scale as well for thousands of redirects (in my experience) and the list becomes append-only, with no owners and redirects everyone is scared to clean up 😆.

That said, it's on our roadmap as a built-in feature for 2025.