Ray
Tue Jul 12 14:10:05 CDT 2005
Hmm, that is an issue. You could also look into custom error pages. It
actually can be as simple as making a page like so:
500.asp:
<html>
<body>
An error occurred. Sorry about that.
</body>
</html>
Put that in the root of your site, then set /500.asp to be the URL of your
error page in IIS for that site. See screen shot of the IIS configuration
here.
http://www.aspfaq.com/show.asp?id=2335
Ray at work
<wolfing1@yahoo.com> wrote in message
news:1121194899.005790.298880@g14g2000cwa.googlegroups.com...
> 1) oh, no I haven't learned HTTPS, I'll get some info on the subject.
> 2) like let's say I call an unexistent stored procedure in the asp
> code, then if I try to go to the page it shows this:
>
> The page cannot be displayed
> There is a problem with the page you are trying to reach and it cannot
> be displayed.
>
> --------------------------------------------------------------------------
------
>
> Please try the following:
>
> Click the Refresh button, or try again later.
>
> Open the localhost home page, and then look for links to the
> information you want.
> HTTP 500.100 - Internal Server Error - ASP error
> Internet Information Services
>
> --------------------------------------------------------------------------
------
>
> Technical Information (for support personnel)
>
> Error Type:
> Microsoft OLE DB Provider for SQL Server (0x80040E14)
> Could not find stored procedure 'createsession'.
> /applications/includes/login/session.inc, line 27
>
>
> Browser Type:
> Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
> 1.1.4322)
>
> Page:
> POST 37 bytes to /applications/login/login.asp
>
> POST Data:
> username=test&pwd=test123&smit=Submit
>
> Time:
> Tuesday, July 12, 2005, 2:12:28 PM
>
>
> More information:
> Microsoft Support
>
>
>
>
> So see there is a section that actually shows the posted fields from
> the form, seems to me that this is dangerous
>