You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
It seems like the language routing to the sitemaps.xml file is not working at all.
I've loaded the nuget packages into my project and configured two sitemaps.
One without language.
One with language.
After having generated my sitemaps in the scheduled job
I see the following behaviour:
The routing for my configuration without without language https://localhost:5001/Sitemap.xml seems to be working fine (I've confirmed this by adding a breakpoint in your GetaSitemapController.Index() endpoint and verifying that my breakpoint is actually triggered) and by confirming that the sitemap.xml is served.
However, the routing for my configuration without language https://localhost:5001/sv/Sitemap.xml does not seem to be working at all. My breakpoint in the GetaSitemapController.Index() endpoint is not triggered at all which leads me to believe there is something wrong with the language routes for the endpoint.
Hi,
It seems like the language routing to the sitemaps.xml file is not working at all.
I've loaded the nuget packages into my project and configured two sitemaps.
One without language.
One with language.
After having generated my sitemaps in the scheduled job
I see the following behaviour:
The routing for my configuration without without language https://localhost:5001/Sitemap.xml seems to be working fine (I've confirmed this by adding a breakpoint in your
GetaSitemapController.Index()
endpoint and verifying that my breakpoint is actually triggered) and by confirming that the sitemap.xml is served.However, the routing for my configuration without language https://localhost:5001/sv/Sitemap.xml does not seem to be working at all. My breakpoint in the
GetaSitemapController.Index()
endpoint is not triggered at all which leads me to believe there is something wrong with the language routes for the endpoint.I think might be related to this issue: #28
The text was updated successfully, but these errors were encountered: