Hey Anders,

Have you tried in your middleware to exist the handler early and not call next? I notice in this blog post this is what he does https://weblog.west-wind.com/posts/2020/Mar/13/Back-to-Basics-Rewriting-a-URL-in-ASPNET-Core which kind of makes sense because you don't want to continue.

Matt

Is it that you you need to put your code that sets the response after the await next()? I say that as your middleware is interested in the responses, so needs to kick-in on the outgoing part.

See this stripped down example illustrating how to log incoming requests and outgoing responses, and how the latter is after the next() call.

Andy

Andy's answer could be a solution.

Otherwise I guess you could do something like this, and add it after the Umbraco middleware:

 public class RedirectFromDBMiddleware
    {
        private readonly RequestDelegate _next;
        private readonly IUmbracoContextAccessor _umbracoContextAccessor;

        public RedirectFromDBMiddleware(RequestDelegate next, IUmbracoContextAccessor umbracoContextAccessor)
        {
            _next = next;
            _umbracoContextAccessor = umbracoContextAccessor;
        }

        public async Task InvokeAsync(HttpContext context)
        {
            var publishedRequest = _umbracoContextAccessor?.UmbracoContext?.PublishedRequest;
            if (publishedRequest is not null && !publishedRequest.HasPublishedContent())
            {
                context.Response.Redirect("/whatever-for-from-db?originalUrl=" + context.Request.Path);
            }
            else
            {
                await _next(context);
            }


        }

Thank you for migrating the package :)

is working on a reply...