Navigation

    What the Daily WTF?

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    1. Home
    2. je44ery
    J
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    je44ery

    @je44ery

    0
    Reputation
    1
    Posts
    10
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    je44ery Follow

    Best posts made by je44ery

    This user hasn't posted anything yet.

    Latest posts made by je44ery

    • Most verbose HTTP 404 message I've ever seen.

       http://www.rsasecurity.com/rsalabs/pkcs/pkcs-12/

       Screen scrape follows.

      Server Error in '/' Application.

              <h2> <i>'//App_Data/redirects/www.rsa.com:80.txt' is not a valid virtual path.</i> </h2></span>
      
              <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">
      
              <b> Description: </b>An
      

      unhandled exception occurred during the execution of the current web
      request. Please review the stack trace for more information about the
      error and where it originated in the code.

              <b> Exception Details: </b>System.Web.HttpException: '//App_Data/redirects/www.rsa.com:80.txt' is not a valid virtual path.<br><br>
      
              <b>Source Error:</b> <br><br>
      
              <table width="100%" bgcolor="#ffffcc">
                 <tbody><tr>
                    <td>
                        <code>
      

      The source code that generated this unhandled exception can only be
      shown when compiled in debug mode. To enable this, please follow one of
      the below steps, then request the URL:

      1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

        <%@ Page Language="C#" Debug="true" %>

      or:

      2) Add the following section to the configuration file of your application:

      <configuration>
         <system.web>
             <compilation debug="true"/>
         </system.web>
      </configuration>


      Note that this second technique will cause all files within a given
      application to be compiled in debug mode. The first technique will
      cause only that particular file to be compiled in debug mode.

      Important:
      Running applications in debug mode does incur a memory/performance
      overhead. You should make sure that an application has debugging
      disabled before deploying into production scenario.

                    </td>
                 </tr>
              </tbody></table>
      
              <br>
      
              <b>Stack Trace:</b> <br><br>
      
              <table width="100%" bgcolor="#ffffcc">
                 <tbody><tr>
                    <td>
                        <code></code><pre>[HttpException (0x80004005): '//App_Data/redirects/www.rsa.com:80.txt' is not a valid virtual path.]<br>   System.Web.VirtualPath.Create(String virtualPath, VirtualPathOptions options) +213<br>   System.Web.HttpServerUtility.MapPath(String path) +33<br>   RSATemplate.TranslateSiteURL(Uri uri) +212<br>   ASP.error404_aspx.Page_Load() +287<br>   System.Web.Util.CalliHelper.ArglessFunctionCaller(IntPtr fp, Object o) +5<br>   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +826911<br>   System.Web.UI.Control.OnLoad(EventArgs e) +99<br>   System.Web.UI.Control.LoadRecursive() +47<br>   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061<br></pre>
      
                    </td>
                 </tr>
              </tbody></table>
      
              <br>
      
              </font></p><hr size="1" width="100%" color="silver">
      

      <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif "> Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832

              </font><p>&nbsp;</p><p>&nbsp;</p>
      posted in Side Bar WTF
      J
      je44ery