That was why I mentioned IIS's built in wildcard redirection - it should do the same job as your module, but it should be faster and place less load on the system (since it runs inside IIS and doesn't require the .NET runtime be loaded for that site).
Geoff On Tue, May 20, 2008 at 1:24 PM, Paul Cowan <[EMAIL PROTECTED]> wrote: > Having this selected will only redirect the page to the appropriate HTTP > error page when you try and request the page over HTTP.I needed to write an > HTTP handler to do the [EMAIL PROTECTED]> Date: Tue, 20 May > 2008 12:47:50 +0100> From: [EMAIL PROTECTED]> Subject: Re: > [ADVANCED-DOTNET] HTTPS> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> > > I > thought there was a 'require SSL' option somewhere in IIS, but I can't> > > find it now so maybe I was thinking of Apache or some other server...> > > There is (assuming IIS6)> > Website or folder properties> Directory Security > tab> Secure communications box -> Press Edit button> > Here you will find > the "Require secure channel (SSL)" checkbox> > It's also present in IIS7, > but can't look for it now> Chris> > ===================================> > This list is hosted by DevelopMentor(R) http://www.develop.com> > View > archives and manage your subscription(s) at http://discuss.develop.com > _________________________________________________________________ > > http://clk.atdmt.com/UKM/go/msnnkmgl0010000009ukm/direct/01/ > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
