93
originating connection was HTTPS or HTTP. This may be important if the application on the
server requires that kind of information.
You can turn on “tag SSL-terminated
HTTP requests.” By selecting “Yes,” the decrypted traffic to the servers will have the added
MIME header “X-WebMux-SSL-termination: true.” It is up to you how you want the server
to process this information. For example, you can write a script on your server to identify if
the original traffic was HTTPS or HTTP, and then properly redirect the traffic to the HTTPS.
The WebMux allows SSL termination for any farm port. If your SSL/TLS traffic is other than
the standard HTTPS traffic, you can specify the SSL port in the
“SSL port” field.
Servers are HTTPS Servers, Re-encryption (Layer 7)
This is only allowed on a farm doing SSL termination. When it is not enabled the forwarded
client connections between the WebMux and the real servers are unencrypted. With this
option enabled, the WebMux will use a secure, encrypted connection between itself and the
real servers. Microsoft® Lync® and Exchange® servers may need this feature.
Servers Only Serve IPv4, Not IPv6 (Layer 7)
If the incoming traffic is IPv6, WebMux can map them into IPv4 servers.
Farm Will Use MAP
If the Multiple Address/Ports feature is going to be used, this must be selected upon creation
of the farm. This cannot be set or disabled once the farm is created. You will need to delete
and recreate the farm to change this. Also, the MAP feature cannot be enabled in
conjunction with any Layer 7 features or the Compress HTTP Traffic feature.
Health Check Port Number (for generic TCP and custom TCP services)
By default, the WebMux will do its custom service check on port 80 no matter what port you
set up for the farm. If you wish to change this, you can specify a port here. This is a global
setting and will be used for all farms using the custom health check service.
Compress HTTP Traffic
Selecting “yes” to this option will activate the WebMux HTTP compression. If the client web
browser sends out a MIME header that states that it accepts compressed data, the WebMux
will compress HTTP data to the client browser. If the WebMux detects that the servers in
the farm are already compressing the data, the WebMux will not perform compression.
Instead, it will let the compressed data from the servers pass through without additional
processing. When enabled the
MIME header “X-WebMux-Compression: true” will be
appended to the server response MIME header.
The WebMux will also automatically disable compression should its CPU usage reach 50%.
The MAP feature cannot be used in conjuction with the compression feature.
