I need to bring an asp or .net web application down, not the entire web site.
The application needs to remain available to select IPs or nt users,
whichever is possible.
Is there a best practice to handling this?
"ghause"
news:862634F7-91DD-4454-98E3-27457B184AAD@microsoft.com...
> I need to bring an asp or .net web application down, not the entire web
site.
> The application needs to remain available to select IPs or nt users,
> whichever is possible.
>
> Is there a best practice to handling this?
I'm not sure about best practice but its possible to limit availability of a
site to specific users by granting access to the root folder and its
contents to a specific user group (in addition to the IUSR_
account). Your selected set of users would be members of the user group.
You can then restrict access by turning off anonymous access.
IIS also allows you to restrict access specific IP addresses via the
Directory Security tab on the site properties dialog in IIS manager.
--
Anthony Jones - MVP ASP/ASP.NET
Hello,
I am not sure i understand what you want to do. You want to bring down an
application, but it must be available to some users. To me, "bring down"
means that you undeploy the application and remove it from the server (to
be able to deploy a new version of the application). You cannot do this if
you want it to be available to some users.
So I assume that "bring down" means something different in this context.
By reading the message, i get the feeling that you just want to restrict
access to the application to certain users, based on IP addresses and/or
user account.
This is possible in IIS. From the Security tab (properties for the website
or virtual directory). From there you can disable anonymous access as well
as add IP address restrictions and allow windows authentication. You will
also need to check NTFS security on the files if you do not want all
authenticated users to access the website.
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
ghause wrote:
>I need to bring an asp or .net web application down, not the entire web
>site.
>The application needs to remain available to select IPs or nt users,
>whichever is possible.
>
>Is there a best practice to handling this?
Its funny you mention this scenario, which is by far a usual one and
normally handled via NLB configurations when they interpret and filter the
http protocol (layer 5?).
However, and probably offtopic related to your case since you did not
mention the runtime of your webapps, there is a quite interesting feature in
ASP.NET 2.0 that re-inforces the xcopy model for deployment.
Its possible to disable an entire ASP.NET webapp (AppDomain) by copying a
very special file - app_offline.htm. Upon copying this file to the root
directory of the VDir in question, ASP.NET no longer processes requests and
only delivers that same file. Useful for "under maintenance" scenarios.
More here:
http://weblogs.asp.net/scottgu/archive/2005/10/06/426755.asp x
Tiago Halm
app_offline was considered, but because it does not work for classic asp, and
blocks all traffic to the application it is really pretty useless in my
situation.
"Tiago Halm" wrote:
> Its funny you mention this scenario, which is by far a usual one and
> normally handled via NLB configurations when they interpret and filter the
> http protocol (layer 5?).
>
> However, and probably offtopic related to your case since you did not
> mention the runtime of your webapps, there is a quite interesting feature in
> ASP.NET 2.0 that re-inforces the xcopy model for deployment.
>
> Its possible to disable an entire ASP.NET webapp (AppDomain) by copying a
> very special file - app_offline.htm. Upon copying this file to the root
> directory of the VDir in question, ASP.NET no longer processes requests and
> only delivers that same file. Useful for "under maintenance" scenarios.
>
> More here:
> http://weblogs.asp.net/scottgu/archive/2005/10/06/426755.asp x
>
> Tiago Halm
>
>
>