Exactly how does the web page perform the redirect: 1. HTTTP 200 with a meta-refresh tag 2. HTTP 302 with a "Location" header ? Link Translation operates on a 302 response even if you have LT disabled for the rule. What's the problem with using SSL all the time? At least this way, you know no one can inadvertently allow sensitive information to be sniffed. From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Crockett, Gregory Sent: Tuesday, August 28, 2007 4:31 AM To: isalist@xxxxxxxxxxxxx Subject: [isalist] HTTP redirect via IIS 6 and ISA 2006 Before the upgrade from 2004, the redirect via IIS worked with no problems. The redirect works internally, but going through ISA 2006 has problems. The redirect: nafjobs.org -> http://www.nafjobs.org. Once at the page, the user selects Login/Register, they should receive https://www.nafjobs.org/core_frames.asp. Since the upgrade to 2006, I had to configure the rule to redirect "http to https". If not redirect, the request would loop and fill the page with the header. TIA greg All mail to and from this domain is scrutinized by the Scrutinizer. All mail to and from this domain is GFI-scanned.