XWEB: Passing 'FRONT-END-HTTPS: on' Custom Header from F5 Networks SSL Gateway to the Front-End Server Does Not Enable an SSL Session in OWA

Article translations Article translations
Article ID: 283195 - View products that this article applies to.
This article was previously published under Q283195
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

Symptoms

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:
FRONT-END-HTTPS: on
However, this procedure does not work with OWA. The back-end server generates "http://" Uniform Resource Locators (URLs) to OWA instead of "https://".

Cause

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.

Resolution

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 the Microsoft 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:

Component: HTTP-DAV

Collapse this tableExpand this table
File nameVersion
Exprox.dll6.0.4418.48

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.

Status

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.

Properties

Article ID: 283195 - Last Review: October 26, 2013 - Revision: 2.0
Applies to
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbqfe KB283195

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com