David
Sun Jan 23 20:04:58 CST 2005
I think the IP Restriction setting in IIS I mentioned earlier should suffice
for this use. You will get to actually target the real URL, and only you --
IIS will actively reject other access with 403.6, which you can rig to
display whatever message you want.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jeremy S." <A@B.COM> wrote in message
news:ephdaiGAFHA.3120@TK2MSFTNGP12.phx.gbl...
<< If you take the website offline, how are you supposed to be able to check
that everything works as planned>>
Great question... and thanks for your feedback. One way I was going to
[check that everything works as planned] would be to have a completely
duplicated Web site that I do have access to (only difference is the URL)...
yes - this would mean I'm not really checking out the exact same Web site as
the one taken offline - but it would certainly allow me to check out all new
app components and back-end database updates in the production environment
while users could not access the app via the "real" URL. Once satisfied that
this "test in production site" is functioning as expected, then I just copy
the updated files over to the "real" production site.
-JS
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:uTjqqMGAFHA.2012@TK2MSFTNGP15.phx.gbl...
> Question: If you take the website offline, how are you supposed to be able
> to check that everything works as planned?
>
> One possibility -- temporarily set up IP Restriction in IIS to only allow
> 127.0.0.1 access to the website and/or application and deny all other
> traffic. This allows you unfettered access to test, but external users
> all
> get the "IP Restriction" custom error 403.6 -- which you can customize to
> point to the "please try again later" page.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "Jeremy S." <A@B.COM> wrote in message
> news:e%23jDtX6$EHA.3528@tk2msftngp13.phx.gbl...
> What would be a good or recommended way to make a Web site in IIS6
> inaccessible to users on the Internet. My situation is that I will
> periodically update this ASP.NET Web application. While I am making the
> update (which will take only a couple of minutes, max) and subsequently
> checking that everything works as planned after the update (which may take
> 5-20 minutes), I don't want any visitors to access any pages in the site.
> Rather, they should get some page that tells them what to expect (e.g.,
> "please try again later" or whatever).
>
> Thanks!
>
>
>