Even with the plugins, you still cannot get the level of functionality that apache's URLRewrite offers. If you just need basic things, the non-free IIS plugin might work for you, but if you need advanced functionality, the only way to go is apache.
Russ > -----Original Message----- > From: Jim Wright [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 01, 2006 6:17 PM > To: CF-Talk > Subject: Re: OT: IIS URL rewriter? > > That makes sense...and is good to know...I had always thought of > URL-rewriting from the SEO aspect...but I can probably find uses for > it with SSL, as IIS's capabilities do leave something to be desired. > > > On 3/1/06, Jim McAtee <[EMAIL PROTECTED]> wrote: > > Actually, I'm doing some similar things in CF, although not to redirect > > 'host.name' to 'www.host.name'. For non-CF content you can use a > > combination of IIS's error handling templates and either CF or ASP, but > it > > gets fairly complicated and is easily broken by configuration changes. > > I'm sure using an ISAP plugin and it doing at the server level is also > > much more efficient than using CF. > > > > For the SSL, yes, I've tried using IIS capabilities, but haven't really > > been able to do what I want. I believe it can be done by a rewriter, > but > > I'll have to see what Dave's recommendation can do. I think you can use > a > > regex to tell it that anything requested using https:// and not under, > > say, '/myaccount/' would be redirected to http://. If I have an SSL > cert > > attached to a web site I always find it difficult making sure that any > > links leaving the secure area do not use SSL. > > > > > > ----- Original Message ----- > > From: "Jim Wright" <[EMAIL PROTECTED]> > > To: "CF-Talk" <[email protected]> > > Sent: Wednesday, March 01, 2006 3:08 PM > > Subject: Re: OT: IIS URL rewriter? > > > > > > > Not having used a URL rewriter, I may be off here, but is it going to > > > solve either one of your issues? The domain.com>>www.domain.com issue > > > can be solved with a 301 redirect...in cf you can detect what the host > > > header is, and then redirect using something like: > > > <cfheader statuscode="301" statustext="Moved permanently"> > > > <cfheader name="Location" value="http://www.domain.com";> > > > > > > And I don't see how a URL rewriter is going to solve the SSL issue. > > > IIS has the ability to require SSL (although not real good > > > capabilities to automatically redirect to https, if I remember > > > correctly). Does a URL rewriter generally give you that kind of > > > control? > > > > > > On 3/1/06, Jim McAtee <[EMAIL PROTECTED]> wrote: > > >> I've noticed a lot of other web sites these days redirecting > > >> http://domain.com to http://www.domain.com. And I've read that > serving > > >> a > > >> web site under both host names may invoke a duplicate content penalty > > >> in > > >> some search engines. > > >> > > >> We'd also like to use a URL rewriter to force certain areas or pages > of > > >> the site, such as http://www.domain.com/myaccount/ to use SSL/https, > > >> while > > >> expressly keeping any other areas of the same site from being served > > >> using > > >> SSL. > > >> > > >> What is a good URL rewriter that can be used with both IIS 5 and IIS > 6? > > >> > > >> > > >> > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:233817 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
