TDWTF error message WTF?



  • The site was down for a couple of hours today, yielding an ASP.NET error page instead of the usual content. For some reason I viewed the source of the page, and here is what I found just below the </html> tag:

    ------------------- 

    [ThreadAbortException]: Thread was being aborted.
       at System.Reflection.AssemblyName.nInit(Assembly& assembly, Boolean forIntrospection, Boolean raiseResolveEvent)
       ... skipped about 30 lines stack-trace ...
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    --><!--
    This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using &lt;customErrors mode="Off"/&gt;. Consider using &lt;customErrors mode="On"/&gt; or &lt;customErrors mode="RemoteOnly"/&gt; in production environments.-->

    ------------------- 

    I guess it's easier to debug this way; but imho this deserves at least "minor wtf" status 



  • Last night around 12:30 am PST the site was down as well, and it was spitting back a 'malformed web.config' error, showing me all sorts of info about the inside of TDWTF's web.config file :)

    -cw



  • [quote user="CodeWhisperer"]

    Last night around 12:30 am PST the site was down as well, and it was spitting back a 'malformed web.config' error, showing me all sorts of info about the inside of TDWTF's web.config file :)

    -cw

    [/quote]

    Yea, too bad we didnt' have access to D:\websites\Alex\DailyWtf.com or a path like that.

    But then, I dont think I might want to look at the customized source code of Community Server anyway.



  • [quote user="Sad Bug Killer"]

    I guess it's easier to debug this way; but imho this deserves at least "minor wtf" status 

    [/quote]

     

    the very fact that they're using ASP is a major WTF 



  • [quote user="Kazan"][quote user="Sad Bug Killer"]

    I guess it's easier to debug this way; but imho this deserves at least "minor wtf" status 

    [/quote]

     

    the very fact that they're using ASP is a major WTF 

    [/quote]

    The Widows and Orphans of the Cold Fusion Flame Wars Foundation beg you... don't say it. :)

    Anyway, it's ASP.NET, which is a few factors better than classic ASP.



  • Not quite sure what was causing that … I think a database deadlock or something. No matter, I restarted IIS and we're obviously back up and running. 

    I’ve enabled these errors on purpose. Config has no sensitive info and it makes debugging and finding problems (developers always send screenshots) so much easier. Besides, would you, as a developer/tech person, prefer to see nothing but a page that says "Unexpected Error Occured" ?



  • [quote user="Alex Papadimoulis"]

    Besides, would you, as a developer/tech person, prefer to see nothing but a page that says "Unexpected Error Occured" ?

    [/quote]

    Personally I'd rather see a pie.

     "Unfortunately the site is down at the moment. Until it is fixed, please look at this pie."
     



  • [quote user="RayS"]

    [quote user="Alex Papadimoulis"]

    Besides, would you, as a developer/tech person, prefer to see nothing but a page that says "Unexpected Error Occured" ?

    [/quote]

    Personally I'd rather see a pie.

     "Unfortunately the site is down at the moment. Until it is fixed, please look at this pie."
     

    [/quote]

     

    ok...that is just so odd im lol 



  • Instead of showing the errors you can implement the Application_Error function if you are using a single web project, or you can override the OnError event if you are using a custom base Page class.  In there you can send an email to yourself containing the detailed error info, or log it in the event viewer.  Below is an example:

     

            protected override void OnError(EventArgs e)
            {
                    try
                    {
                        Exception exMyError = Server.GetLastError();

                        exMyError = exMyError.GetBaseException();

                       //SEND THE EMAIL OR LOG INTO EVENT VIEWER
                    }
                    catch(Exception)
                    {

                    }
                    finally
                    {
                        //SEND THEM TO THE ERROR PAGE             
                    }

                base.OnError (e);
            }



  • The real WTF is that someone has just actually tried to help, instead of just pointlessly bitching about Microsoft and ASP and .NET and security. ;)



  • The real WTF is that the Daily WTF real WTF err... OH GOD I CAN SEE THE FUTURE



  • you got it all wrong, community server IS the REAL WTF



  • Having some experience with ASP.NET, I know it is possible to show the public a custom error message and still be able to see the real error yourself when you check the page on the server itself.

     Just put in your web.config file ' <customErrors mode="RemoteOnly"/ ' . An error message like that looks strange to the average visitor who does not know what it is.



  • You are all wrong.

     

    The real WTF is the inflationary use of "the real WTF is...". 



  • [quote user="R.Flowers"]

    Anyway, it's ASP.NET, which is a few factors better than classic ASP.

    [/quote]

     

    it's still a microsoft-dependant crappy language



  • [quote user="Kazan"][quote user="R.Flowers"]

    Anyway, it's ASP.NET, which is a few factors better than classic ASP.

    [/quote]

     

    it's still a microsoft-dependant crappy language

    [/quote]

    ASP.NET is a language, then? Nice to see that your bashing is entirely lacking facts or accuracy.It also doesn't require Microsoft, due to Mono, etc. It's also a very solid product.

     At least you got the "it's" part right.



  • [quote user="RayS"]

     At least you got the "it's" part right.

    [/quote]

     

    Its.....Monty Pythons "Flying circus" 



  • [quote user="RayS"][quote user="Kazan"][quote user="R.Flowers"]

    Anyway, it's ASP.NET, which is a few factors better than classic ASP.

    [/quote]

     

    it's still a microsoft-dependant crappy language

    [/quote]

    ASP.NET is a language, then? Nice to see that your bashing is entirely lacking facts or accuracy.It also doesn't require Microsoft, due to Mono, etc. It's also a very solid product.

     At least you got the "it's" part right.

    [/quote]

     

    last i checked mono exist only at M$'s sufferance, ASP is a language, .NET is a framework [and a shitty one at that]

     

    If ASP.NET is "a solid product" then I have a 12 FOOT long wang.     



  • [quote user="Kazan"]

    If ASP.NET is "a solid product" then I have a 12 FOOT long wang.     

    [/quote]

    Hmm, on that scale I would have to put your "Wang" at around the 10 foot mark!  (although even if you think it only deservs a 1 out of 10, you're still going to be doing push ups without using your hands.)

     



  • [quote user="Kazan"]

    If ASP.NET is "a solid product" then I have a 12 FOOT long wang.     

    [/quote]

    Hmm, on that scale I would have to put your "Wang" at around the 10 foot mark!  (although even if you think it only deservs a 1 out of 10, you're still going to be doing push ups without using your hands.)

     


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.