If you add the /api/ url to Umbraco.Core.ReservedUrls setting it should be ok again. Alternative you can also add /api/* to app_plugins/seochecker/config/botfilter.config
I have a similar problem here with normal ASP.NET bundles like "/bundles/css/non-critical?v=" that redirected to "/bundles/css/non-critical/?v=" which results in a 404.
I have "~/bundles/" in "Umbraco.Core.ReservedPaths" already, which doesn't work. Also tried to add "~/bundles/" to "Umbraco.Core.ReservedUrls" but no luck there either.
I think I have tried every different path now and still doesn't work.
/bundles/css/non-critical?v=TxvBE6HNcv0-FfivwjS0Mof41D7aTN3LXLNpz5ESinE1 gets a 301 to /bundles/css/non-critical/?v=TxvBE6HNcv0-FfivwjS0Mof41D7aTN3LXLNpz5ESinE1
Which Umbraco version do you have? I have Umbraco 8.18.5.
Disable trailing slash for path or method
Hi Richard!
I'm using SEO Checker on a website that also have a web api configured.
So a PATCH request to /api/products/1 would be redirected to /api/products/1/ which does not route to the right endpoint.
Is there a way to disable the force trailing slash-settings ie. for /api/ ? Or maybe for PATCH-methods? It looks like POST-method does work.
// m
Hi Markus,
If you add the /api/ url to Umbraco.Core.ReservedUrls setting it should be ok again. Alternative you can also add /api/* to app_plugins/seochecker/config/botfilter.config
Hope this helps,
Richard
I have a similar problem here with normal ASP.NET bundles like "/bundles/css/non-critical?v=" that redirected to "/bundles/css/non-critical/?v=" which results in a 404.
I have "~/bundles/" in "Umbraco.Core.ReservedPaths" already, which doesn't work. Also tried to add "~/bundles/" to "Umbraco.Core.ReservedUrls" but no luck there either.
Version of SEO Checker: 2.11.2
Any ideas?
Hi Erik,
This did the trick for me.
I think I have tried every different path now and still doesn't work.
/bundles/css/non-critical?v=TxvBE6HNcv0-FfivwjS0Mof41D7aTN3LXLNpz5ESinE1
gets a 301 to/bundles/css/non-critical/?v=TxvBE6HNcv0-FfivwjS0Mof41D7aTN3LXLNpz5ESinE1
Which Umbraco version do you have? I have Umbraco 8.18.5.
8.14 But should be the same. 301 redirects are cached byu the browser so that might be the issue as well.
It actually works if you only have
or
but not if you have a comma separated list which should be supported
So there seems to be a bug around this.
Hi ERik,
Is fixed for next release. Beta can already be used https://www.nuget.org/packages/SEOChecker/2.11.4-beta2
Hope this helps,
Richard
Thanks for the fast response Richard!
ReservedUrls did the trick =D
// m
is working on a reply...