Shannon has been working to update Articulate to v8 and I don't know if any of these actually work at the moment, but you might spot the difference between your implementation and his:

This one looks the simplest: https://github.com/Shazwazza/Articulate/blob/v8/src/Articulate/Controllers/WlwManifestController.cs

And then there's: https://github.com/Shazwazza/Articulate/blob/v8/src/Articulate/Controllers/MarkdownEditorController.cs https://github.com/Shazwazza/Articulate/blob/v8/src/Articulate/Controllers/FeedController.cs https://github.com/Shazwazza/Articulate/blob/v8/src/Articulate/Controllers/OpenSearchController.cs https://github.com/Shazwazza/Articulate/blob/v8/src/Articulate/Controllers/RsdController.cs

And attributed controllers: https://github.com/Shazwazza/Articulate/blob/v8/src/Articulate/Controllers/ThemeTreeController.cs https://github.com/Shazwazza/Articulate/blob/v8/src/Articulate/Controllers/ThemeEditorController.cs

Hope it helps and if it does, do update this post so others can learn too! 👍

Thanks! I've had a look and can't see anything I've missed - the implementations do look similar. I think I'm going to have to pull down Articulate and see if they work.

OK for anyone who may be following the thread, I think I've found the issue.

The routes in Articulate appear to be working as expected. I noticed that the only real difference between the two implementations is that my implementation contains a file extension (e.g. .xml) in the route url.

So in short this will work:

routes.MapRoute(
    "SitemapXml",
    "sitemap",
    new
    {
        controller = "Sitemap",
        action = "Xml"
    }
);

This will cause the error to be thrown:

routes.MapRoute(
    "SitemapXml",
    "sitemap.xml",
    new
    {
        controller = "Sitemap",
        action = "Xml"
    }
);

As mentioned the file extension version works in v7 so could well be a bug, or something else needs to be considered.

-lewis

No, unfortunately I didn't find a solution in the end. I ended up just using a extension-less URL for my sitemap and declaring it in robots.txt.

I've not re-visited the issue since but I am pretty sure this is a bug specifically to do with the Umbraco PluginController, as my robots.txt is also dynamically generated using a standard Mvc Controller and is accessed via a route with a .txt extension, and that works fine.

With this reminder I'll raise an issue :)

You can find two other solutions here https://umbracians.slack.com/archives/C06G5LWBV/p1572021036469000.

Cheers

MVC doesn't allow you to route "static" paths (anything with a full-stop character) by default, so a non-Umbraco option is to tell IIS to let those requests through to be routed:

https://stackoverflow.com/questions/2006529/mvc-how-to-route-sitemap-xml-to-an-actionresult

However, this sometimes then has issues with Umbraco's context and service resolution, so I find the easiest way is to do a quick IIS rewrite instead:

Component:

routes.MapRoute(
    "SitemapXml",
    "sitemap-xml",
    new
    {
        controller = "Sitemap",
        action = "Xml"
    }
);

web.config:

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

is working on a reply...