a certain url corruption will crash w3wp.exe. a user repeatedly entered this url http://www.mywebsite.info/home/the-xxxxxxxxxxxx-of-xxxxxxxx-xxxxxxx-xxxxxx.aspx?ArticleId=52'A=0&tabid=514 . wherever there is x, I have replaced real data to minimize further attacks upon my website. the offending string is 'A=0. removing it generates a valid url. when submitted, dnn fails with a page load exception and the message A critical error has occurred. Please check the Event Viewer for further details. 3-4 page refreshes with this corrupt url causes w3wp.exe to crash and pop open visual studio debugger on the server.
the url is attempting to go to a page managed by live articles.
There is a lot going on in any dnn site. I could not begin to assign culpability because I am running dnn 8.0.1, dnn sharp url adapter, live articles, iis 7.5, and god knows what else which could impinge upon the failure.
one of the errors is
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at Mandeeps.DNN.Modules.LiveArticles.UI.LiveArticlesWidget.View.#d()
at Mandeeps.DNN.Modules.LiveArticles.UI.LiveArticlesWidget.View.Page_Load(Object sender, EventArgs e)
at DotNetNuke.Entities.Modules.PortalModuleBase. (EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
the LoadRecursive() probably put w3wp.exe over the edge - just speculation.
I suppose ultimately w3wp.exe should be more resilient, but I don't know what is going on under the covers. does anyone know of a remedy or prevention for this problem? I will probably take it to the module publisher.