Deny Domain Access

[Galahad]

I have a current requirement to deny access to a particular website from a
list of domains. I can add these domains to a deny list in IIS, however that
doesn't give me the ability detect these domains and then redirect users to
specific deny pages based on the domains to which they are members.

I can include a function on all of my webpages to detect the various domains
and redirect users, however this would be a very tedious process since I
would have to include this domain validation function on all pages.

I need to find a better more efficient way of doing this, so any suggestions
are welcome...

 

[Sven Pernils]

There are softwares that you can install in IIS that does the trick, but
there's nothing wrong to include a file in every page, where you can
validate domains, users etc. But that on the other hand requiers a domain
search. That can be done, but requiers a little more coding, and to find a
stable domain search site, and do a domain lockup for every page shown.
That's not so good.

Sven

 

[Jeff Cochran]

I have a current requirement to deny access to a particular website from a
list of domains. I can add these domains to a deny list in IIS, however that
doesn't give me the ability detect these domains and then redirect users to
specific deny pages based on the domains to which they are members.

I can include a function on all of my webpages to detect the various domains
and redirect users, however this would be a very tedious process since I
would have to include this domain validation function on all pages.

I need to find a better more efficient way of doing this, so any suggestions
are welcome...

Without writing an ISAPI filter for this, you would need to validate
on each page that could be accessed, meaning an include in your case.
An alternative would be a custom error page that redirects based on
referrer, using a 403 error (403.8?) when the access is denied.
Google for custom IIS error pages for docs on doing this.

Jeff