Web Applications

[prev] [thread] [next] [lurker] [Date index for 2005/09/07]

From: Robert Spier
Subject: Web Applications
Date: 04:25 on 07 Sep 2005

Dear $TICKET_VENDOR,

    The below message is not useful.

    It does not tell me why I was unable to buy tickets from you.

    It does not tell me who to contact.

    But worst of all, when I get this message, it means I cannot buy
    $100 tickets from you for the privilege of paying a $7.50
    convenience fee.

    Maybe you don't like FireFox?  I know you don't like Safari.  I
    tried Internet Explorer, but it crashed.  (That's not your fault.)

    Thanks-  

-R

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Generated at 17:00 on 07 Sep 2005 by mariachi 0.52