IIS 404 Error DLL Invoking Question

[Joe Apato]

Here is my set up:

Windows 2000 server running Coldfusion. I have to corporate webs on this
server. Web 1 is a normal web (nothing special, web 2 is a virtual web under
web 1 WITH SSL.

I am setting up custom error pages, some with Coldfusion in them and some
with out. On web 1 everything works OK. On web 2 (with is a virtual under web
1 and secured with SSL) my problem is when I point the custom error page to a
custom HTML only file I get send to an unfriendly 404 page that is generated
by a DLL. I figured out it was by a DLL because when I properties the page
the URL simular to https://www.mydomain.com/DLL?*********

I can't remember the rest. I know it is dll invoked.

How do I shut down the DLL invoked 404 page?

Please send responses to joe....@ngc.com

Thanks for your help!!!

[David Wang [Msft]]

If you configured custom error page to a .HTML page but did not get its
content as a response, there is some 3rd party ISAPI on the machine that is
generating that content. You will need to find and configure that component
to stop doing that. How to do this -- completely depends on the component,
which you should know about.

If you configured custom errors to a file which contains and is processed by
Cold Fusion but did not get the expected content, then you have Cold Fusion
misconfigured on this web and should obtain support from Macromedia
concerning their product.

The default configuration for 404 custom error does not result in what you
see nor does it behave the way you claim, so there is definitely some user
misconfiguration.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Joe Apato" <JoeA...@discussions.microsoft.com> wrote in message
news:E4A14128-5F13-4D9D...@microsoft.com...

[Joe Apato]

Correction, it is a 403.1 error.

User A is not in the ACL for a sub web. When they try to go to that subweb
and try to authenticate into that web, they fail and are sent to the 403.1
page. The 403.1 error page that is generated is the unfriendly page generated
by a DLL

[David Wang [Msft]]

Ok, it is very important for you to give me the correct error
status/substatus because it completely changes how to diagnose the problem.
It's like as if a program is crashing and you told me it was because a file
is missing instead of the user not having read access to the file -- two
totally different things with different diagnosis.

If it is a 403.1, then it means that the subweb lacks "Scripts" or "Scripts
and Executable" Execution Permission when IIS was asked to execute a request
that required such permission.

What is happening is that on your request, IIS notices that it needs to call
Cold Fusion (or whatever other program) to process the request, but since
"Scripts" or "Scripts and Executable" Execution Permission is not set, the
configuration forbids IIS to execute the request and instead return a 403.1
informing the user of this issue.

Of course, this only prevents the user from incorrectly getting the custom
error page, but it still sounds like you have a configuration issue with the
actual content of the custom error page. That is something for you to
correctly configure on the server -- default custom errors do not behave as
you claim, so something has already been incorrectly configured.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Joe Apato" <JoeA...@discussions.microsoft.com> wrote in message

news:BC19968F-1579-4D6C...@microsoft.com...