http://blogs.isaserver.org/shinder/2006/09/21/redirecting-http-requests-to-ssl-requests-using-the-2006-isa-firewall/ Written by Dr Thomas W Shinder, consultant to Microsoft, HP and many Fortune 500 companies on ISA firewall and Web proxy deployments this blog is where administrators get information about ISA Server Universal Threat Management firewalls. Topics include how to manage, deploy, and troubleshoot ISA Server as a network firewall, Web proxy/Web cache, remote access VPN server and VPN gateway to provide a high level of network security for all corporate computers. Fri, 29 Aug 2008 17:33:43 +0000 http://wordpress.org/?v=MU http://blogs.isaserver.org/shinder/2006/09/21/redirecting-http-requests-to-ssl-requests-using-the-2006-isa-firewall/#comment-16855 Wed, 01 Nov 2006 12:46:57 +0000 http://blogs.isaserver.org/shinder/2006/09/21/redirecting-http-requests-to-ssl-requests-using-the-2006-isa-firewall/#comment-16855 [...] With ISA Server 2006 the solution to redirect the HTTP requests to SSL (HTTPS) requests is very easily implemented by properly configure the Connections properties of the Web Listener as explained in Tom’s blog Redirecting HTTP Requests to SSL Requests using the 2006 ISA Firewall. One of the solutions to redirect the users to the /Exchange folder was to include a special path mapping translating the root path “/” to the special Exchange path “/Exchange”. However with ISA Server 2006 this is no longer possible because it generate the Event ID 21177 as mentioned in my previous blog ISA Server 2006 and KB917025 and the following ISA Alert: [...] […] With ISA Server 2006 the solution to redirect the HTTP requests to SSL (HTTPS) requests is very easily implemented by properly configure the Connections properties of the Web Listener as explained in Tom’s blog Redirecting HTTP Requests to SSL Requests using the 2006 ISA Firewall. One of the solutions to redirect the users to the /Exchange folder was to include a special path mapping translating the root path “/” to the special Exchange path “/Exchange”. However with ISA Server 2006 this is no longer possible because it generate the Event ID 21177 as mentioned in my previous blog ISA Server 2006 and KB917025 and the following ISA Alert: […]

]]>