The URL Rewriting extension in IIS has been replaced with the URL Rewriting Middleware for ASP.NET Core. You can find documentation at https://docs.microsoft.com/en-us/aspnet/core/fundamentals/url-rewriting

Thanks for the help Benjamin.

I changed the startup.cs to look like this:

    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }

        app.UseUmbraco()
            .WithMiddleware(u =>
            {
                u.WithBackOffice();
                u.WithWebsite();
            })
            .WithEndpoints(u =>
            {
                u.UseInstallerEndpoints();
                u.UseBackOfficeEndpoints();
                u.UseWebsiteEndpoints();
            });

        ApplyRewriteRules(app);
    }

    private static void ApplyRewriteRules(IApplicationBuilder app)
    {
        using (StreamReader iisUrlRewriteStreamReader =
            File.OpenText("IISUrlRewrite.xml"))
        {
            var options = new RewriteOptions()
                .AddIISUrlRewrite(iisUrlRewriteStreamReader);

            app.UseRewriter(options);
        }

        app.UseStaticFiles();
    }

I also added a IISUrlRewrite.xml file to the project root (not wwwroot) with the following:

<rewrite>
  <rules>
    <rule name="Sitemap.xml rewrite" stopProcessing="true">
      <match url="^sitemap.xml$" />
      <action type="Rewrite" url="/xml-sitemap" appendQueryString="false" />
    </rule>
  </rules>
</rewrite>

When I hit /sitemap.xml I get a page displaying "Status Code: 404; Not Found".

How can I get this to work?

Hi Brendan

Are you running the site in IIS or through Kestrel? If through Kestrel, you can't use IIS Url rewrites AFAIK. You have to implement redirects/rewrites through code in the middleware.

Hi all,

Rather than creating another thread, I'll add to this - I'm actually facing a similar issue with V9 URL Rewrites.

I've followed this - https://docs.microsoft.com/en-us/aspnet/core/fundamentals/url-rewriting?view=aspnetcore-5.0, minus the xml and txt files but the URL's are still not rewriting.

I've done the following:

        public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }

        app.UseUmbraco()
            .WithMiddleware(u =>
            {
                u.WithBackOffice();
                u.WithWebsite();
            })
            .WithEndpoints(u =>
            {
                u.UseInstallerEndpoints();
                u.UseBackOfficeEndpoints();
                u.UseWebsiteEndpoints();
            });

        // URL Rewrites
        var rewrite = new RewriteOptions()
            .AddRewrite("^sitemap-xml", "/sitemap.xml", true)
            .AddRewrite("^sitemapxml", "/sitemap.xml", true);
        app.UseRewriter(rewrite);
        app.UseRouting();
        app.UseStaticFiles();
    }

And still get the 404 error, whereas in the previous versions via IIS, it would rewrite.

Is there anything I'm missing?

Thanks

Hi Javz :)

The order that the middleware is added in the configuration method is also the order that they'll be processed for requests as responses. It's like a pipeline, so the requests pass through the pipe from the top of what we've declared down to the bottom.

At any point along the pipeline, middleware can choose to return without passing on to the next point in the chain. For example, with authentication, if someone isn't authenticated, the authentication middleware can just terminate the pipeline and return with an error message because calling the rest of the middleware would be pointless. Microsoft have some diagrams in the documentation showing how requests pass down through each layer of middleware and then the response comes back up through the middleware from the bottom to the top.

I'm sill playing with Umbraco 9 but I wonder if its because the Umbraco middleware is not finding a page in the CMS for the sitemap, returning a 404 and terminating so that the rest of the middleware isn't processed?

What happens if you move the rewrite higher up the pipeline like this?

 public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }


    // URL Rewrites
    var rewrite = new RewriteOptions()
        .AddRewrite("^sitemap-xml", "/sitemap.xml", true)
        .AddRewrite("^sitemapxml", "/sitemap.xml", true);
    app.UseRewriter(rewrite);

    app.UseStaticFiles();

    app.UseUmbraco()
       .WithMiddleware(u =>
       {
           u.WithBackOffice();
           u.WithWebsite();
       })
       .WithEndpoints(u =>
       {
           u.UseInstallerEndpoints();
           u.UseBackOfficeEndpoints();
           u.UseWebsiteEndpoints();
       });
     }

The idea that being when the request comes in, the rewrite engine middleware processes the request first, realises that it's got a matching rule and then rewrites the request before we get to Umbraco.

I am facing the same issue.

I would like to ask, does it matter if the xml page is called sitemap-xml and not sitemap.xml?

In the view I am generating the sitemap I am adding this value to the header Content-Type

@{
    Layout = null;
    Context.Response.Headers.Remove("Content-Type");
    Context.Response.Headers.Add("Content-Type", "text/xml");
}  

and I will add a robots.txt which will look like this one

User-agent: *
Disallow: /bin/
Disallow: /config/
Disallow: /install/
Disallow: /umbraco/
Disallow: /views/

Sitemap: https://{domain}/sitemap-xml/

So, Do I need my sitemap to be called "sitemap.xml" ???

Did anyone figure this out?

I've got the below, but get a Status Code: 404; Not Found if I visit https://localhost:44387/sitemap.xml or any other items.

var options = new RewriteOptions()
                .AddRedirectToHttpsPermanent()
                .AddRewrite("robots.txt", "/robotstxt/", true)
                .AddRewrite("sitemap.xml", "/sitemapxml/", true)
                .AddRewrite("images/site.webmanifest", "/Umbraco/Surface/Webmanifest/Render", true)
                .AddRewrite("images/browserconfig.xml", "/Umbraco/Surface/BrowserConfig/Render", true);

app.UseRewriter(options);

The correct answer for me was changing the order of the middleware suggested by @Andy Hale.

Move your app.UseRewriter(options) section above the app.UseUmbraco() section.

If you're running the site in IIS then you can use the same method for V9 - I just added a simplified web.config to the root of the 'publish' folder:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" arguments=".\projectName.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
      <rewrite>  
          <rules> 

           <rule name="Redirect to HTTPS" stopProcessing="true">
              <match url="(.*)" />
              <conditions>
                <add input="{HTTPS}" pattern="^OFF$" />
              </conditions>
              <action type="Redirect" url="https://{HTTP_HOST}/{R:1}" />
            </rule>

        <rule name="^sitemap.xml$" stopProcessing="true">
          <match url="^sitemap.xml$" />
          <action type="Rewrite" url="/search-engine-sitemap/" appendQueryString="false" />
        </rule>

        <rule name="^projects/category/(.*)/" stopProcessing="true">
          <match url="^projects/category/(.*)/" />
          <action type="Rewrite" url="/projects/?category={R:1}" appendQueryString="false" />
        </rule>


        </rules>
      </rewrite>
    </system.webServer>
  </location>
</configuration>

is working on a reply...