David
Fri Aug 26 08:21:24 CDT 2005
No, one website without SSL doesn't make sense. When you give a URL Custom
Error, the defining website is implied in the URL, so no way to redirect to
another website (that doesn't make sense anyways -- SERVER_NAME won't be
correct for the redirect, either).
See the approach described in this blog entry (Except in your case, you want
to disable SSL instead of enable SSL on a particular URL). Since you are
using URL custom error, you need to apply the IIsWebFile once for every
single website so that the URL shows up in that website.
http://blogs.msdn.com/david.wang/archive/2005/08/13/HOWTO_Use_IIsWebFile_to_fine_grain_control_IIS_behavior.aspx
It has to be this way because URL Custom Error has to execute in some
website's context, and you want it to be in the source website (so that
SERVER_NAME resolves correctly). Thus, it is treated like a URL in every
website, though as I have shown, IIsWebFile can take care of that.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"MLi" <MLi@discussions.microsoft.com> wrote in message
news:E6CD2022-79C6-43C3-A2C2-0F2DE9057E8A@microsoft.com...
But I still have to left one website without SSL?
"David Wang [Msft]" wrote:
> Exact same instructions as the KB article, just apply the Custom Error
> change at global level (right click property on Websites) instead of
> per-website.
>
> This change will only take effect if you let it inherit to all child
> websites (which is the default behavior unless you have customized the
> Custom Errors at a child website/vdir). If you have customized settings,
you
> must hand merge them yourself for each such customized node (UI allows you
> to do #1 or #2 -- it does not merge since that cannot be done in an
> automatic fashion at all) -- if you do not merge, you either:
> 1. Lose the customized settings when you let the global setting override
> 2. Ignore the global setting since you kept the customized local setting.
>
> --
> //David
> IIS
>
http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> //
> "MLi" <MLi@discussions.microsoft.com> wrote in message
> news:4A3A975E-5131-4FF9-9B88-486E2CC89674@microsoft.com...
> How I do redirect http to https for all websites? I have IIS 6.0 and made
> redirect as in kb555126. Now I have to make redirect at Root Directory
> Level.
>
>
>