Re: Prevent a ISAPI DLL to be accessed externally in IIS 6
- From: David Wang <w3.4you@xxxxxxxxx>
- Date: Fri, 19 Oct 2007 11:38:09 -0700
Sure, you can do what you want.
However, I'm confused. If you only want the ISAPI DLL to be accessed
from the server itself, then why did you make it an ISAPI?
This restriction appears to only allow other server-side applications
to invoke the ISAPI, at which point why don't you just make it a plain
Win32 DLL which the applications load.
Or do you actually want to have a web application, just restricted in
this instance.
You can configure IIS to restrict requests by IP with an allow or deny
mask.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Oct 19, 10:56 am, toolsandco...@xxxxxxxxx wrote:
Hello:
I have a ISAPI DLL in my server and I want to prevent people to access
it externally, only from the server itself.
Ex: someone has a website on server X and their HTMLs are accessing a
DLL hosted on my server.
Can I prevent it?
Thanks in advance...
Jackson Gomes
.
- Follow-Ups:
- Re: Prevent a ISAPI DLL to be accessed externally in IIS 6
- From: toolsandcomps
- Re: Prevent a ISAPI DLL to be accessed externally in IIS 6
- References:
- Prevent a ISAPI DLL to be accessed externally in IIS 6
- From: toolsandcomps
- Prevent a ISAPI DLL to be accessed externally in IIS 6
- Prev by Date: Prevent a ISAPI DLL to be accessed externally in IIS 6
- Next by Date: Re: Prevent a ISAPI DLL to be accessed externally in IIS 6
- Previous by thread: Prevent a ISAPI DLL to be accessed externally in IIS 6
- Next by thread: Re: Prevent a ISAPI DLL to be accessed externally in IIS 6
- Index(es):
Relevant Pages
|