This article was previously published under Q283195
This article has been archived. It is offered "as is" and will no longer be updated.
When you use F5 Networks Big-IP to support a hosted commercial e-mail service that runs Microsoft Outlook Web Access (OWA) over Secure Sockets Layer (SSL), the SSL gateway (F5 Networks Big-IP) may stop the SSL session between OWA and the F5 Networks computer. Communications between the F5 Networks computer and the front-end servers work correctly.
When SSL is used with F5 Networks Big-IP, F5 Networks Big-IP passes the following custom header to the front-end servers:
However, this procedure does not work with OWA. The back-end server generates "http://" Uniform Resource Locators (URLs) to OWA instead of "https://".
This problem occurs because F5 Networks Big-IP passes the custom header "FRONT-END-HTTPS: on" to the front-end servers. The front-end servers generate an additional "FRONT-END-HTTPS: on" header; therefore, the front-end server passes "FRONT-END-HTTPS: on,on" to the back-end server. The back-end server cannot process this header, which results in the generation of "http://" URLs to OWA.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:
NOTE: To fix this problem, you must be using F5 Networks Big-IP version 3.3.1 or later. This fix needs to be applied to all of the front-end servers.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.