We have SEOChecker installed on one of our sites and we get keep a bunch of the same errors in the log, for instance, in the last 24 hours we've had circa 50,000+ of these same errors:
SEOChecker: SEOChecker: Error in UrlRewriteRedirectsProvider for url rewriting
Exception
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.AbortCurrentThread()
at System.Web.HttpResponse.Redirect(String url, Boolean endResponse, Boolean permanent)
at SEOChecker.Providers.UrlProviders.UrlRewriteRedirectsProvider.RewriteUrl(UrlBuilder builder, UrlRewriteConfiguration config)
Really weird that it comes up now. Is in there for years and default behaviour when you redirect in .net and handled will see if it is related to a .net version I assume you are on 4.7.2?
I think a change in asp.net Framework. This happened years ago and a fix for that was implemented but think some regression in .net framework is causing this again.
But will make sure this is on the agenda later this week.
SEOChecker : Error in UrlRewriteRedirectsProvider
Hi,
We have SEOChecker installed on one of our sites and we get keep a bunch of the same errors in the log, for instance, in the last 24 hours we've had circa 50,000+ of these same errors:
We're using:
Does anyone know how to resolve this?
Thanks
Bijesh
Hi Bijesh,
Really weird that it comes up now. Is in there for years and default behaviour when you redirect in .net and handled will see if it is related to a .net version I assume you are on 4.7.2?
Best,
Richard
Hi Richard
Thank you for getting back to me. Yes the project is built against .net 4.7.2.
Also, it's hosted in Azure in an app service.
Other details that might help, it's a multisite solution in one Umbraco instance (same client) and also multilingual.
Thanks
Bijesh
Hi Richard
Were you able to get any further with this? We're still experiencing these errors on a daily basis.
Thanks
Bijesh
I will disable the log for that exception in 2.10.
Thanks Richard.
Is there a reason why this might be happening anyway? Some configuration issue or otherwise?
Thanks
Bijesh
Hi Bijesh,
I've fixed this issue. RC2 of 2.10 can be found here https://www.dropbox.com/s/eubnvrg46uxha18/seo-checker210_0.zip?dl=0
Hope this helps,
Richard
I think a change in asp.net Framework. This happened years ago and a fix for that was implemented but think some regression in .net framework is causing this again.
But will make sure this is on the agenda later this week.
is working on a reply...