That's best done inside IIS. Create a virtual website that is just HTTP. Make the site just a redirector to the "real" site (that is only running HTTPS. This way you can actually share a single IP. You can also accomplish a similar solution via host-headers, if you're using different FQDNs. Hint: you can make the HTTP-only site listen for SSL on a different port (or remove it), and the HTTPS-only site listen for HTTP on a different port. Cheers! -----Original Message----- From: Allisson C. Silva [mailto:allisson@xxxxxxxxxxx] Sent: Monday, November 04, 2002 9:59 AM To: [ISAserver.org Discussion List] Subject: [isalist] Forcing SSl http://www.ISAserver.org Hi guys, I need a aid to force a redirect http://www.domain.com.br\exchange to https://www.domain.com.br\exchange whithout user interaction. That's possible??? If yes which the procedure. Since i thanks any aid. Allisson Cândido Administrador de Rede Flag Informática S/C Mcse Mcsa Mcp Fcp ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: davidh@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')