Coyote Point Systems Equalizer GX Series, Руководство администратора

Страница: 483 / 866

The simplest form of HTTPS redirect involves simply referring the user to the top level of the
https:// site, regardless of the path information that may have been included in the original
request URL. For example, we could direct all requests for:
http://www.example.com/<path>
to:
https://www.example.com
But, this forces the client to re-specify the <path> after the redirect. It would be better to redirect
to a URL that includes the path information:
https://www.example.com/<path>
The following regular expression:
^(([^ :/?#]+):)?//(.*)
breaks a request URL into the following named variables:
$0 http://www.example.com/ <path>
$1 http
$2 http:
$3 www.example.com/<path>
We can then use these variables in the URL field as shown in the following Responder
Configuration
screen (tab):
This Responder can be used in any cluster where a Redirect to an HTTPS cluster is desired.
Example 2 - Multi-Hostname Redirect
Let’s assume that we have a set of ".com" host names, all of which resolve to the same cluster IP,
and we need a Responder that redirects requests to the same hostname prefixes with a ".net"
suffix. We also want to include the rest of the URL exactly as specified by the client. For example,
we want requests to URLs in these formats:
http://www.example.com/ <path>
http://www.example2.com/ <path>
http://www.example3.com/ <path>
to be redirected to the following URLs:
http://www.example.net/ <path>
http://www.example2.net/ <path>
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved. 483
Equalizer Administration Guide