Coyote Point Systems Equalizer GX Series, Administration Manual

Page: 377 / 866

For server connections that contain multiple server responses, the setting of the
once only
flag
determines whether Location: headers in all server responses are rewritten. This is shown in the
table below.
Note that the GUI does not permit you to enable
once only
and disable
no header rewrite
-- this
option combination would rewrite the
Location:
header in only the first response in the
connection, and not rewrite the headers in subsequent responses in the same connection. Doing
so would produce errors on the client.
Of course, you can also direct Equalizer to pass responses from the server without rewriting URLs
by enabling the
no header rewrite
flag on the cluster.
once only
enabled once only
disabled
no header rewrite
disabled
Not supported.
The Location: headers of every response in a connection
are rewritten.
no header rewrite
enabled No headers are
rewritten.
No headers are rewritten.
Specifying a Custom Header for HTTP/HTTPS Clusters
Some applications require specific headers in incoming client requests, and Equalizer provides the
custom header field in HTTP and HTTPS clusters to allow you to inject a custom header into the
client request before it is sent to a server behind Equalizer.
An example is the Exchange 2003 version of Microsoft Outlook Web Access (OWA). OWA 2003
normally requires that all incoming client requests use the Secure Sockets Layer (SSL) protocol.
This means that all client requests must have the
https://
protocol in the URI. If, however, OWA
is running on a server in an Equalizer Layer 7 HTTPS cluster, then OWA will receive all requests
with
http://
in the URI, since Equalizer performs SSL processing before passing the requests on
to the server.
OWA 2003 allows for SSL off loading through the use of a special header, as explained in the
following Microsoft technical article:
http://technet.microsoft.com/en-us/library/578a8973-dc2f-4fff-83c6-
39b1d771514c.aspx
Two things are necessary when running OWA 2003 behind Equalizer:
1. Configure OWA to watch HTTP traffic for requests containing a custom header that indicates
that the request was originally an SSL request that was processed by SSL off loading hard-
ware (i.e., Equalizer) before reaching OWA (see the above article for instructions)
2. Configure the Equalizer cluster to add the custom header to all requests before sending
them on to the OWA server (this is explained below)
The following procedure shows you how to add a custom header to an existing HTTPS cluster
definition, using the header required for an OWA 2003 server as an example.
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved. 377
Equalizer Administration Guide