Mapping and Redirection
| Serve Mapped Hosts Only | Select Required if you want the proxy to serve requests only to origin servers listed in the mapping rules of the remap.config file. If a request does not match a rule in the remap.config file, the browser receives an error. This option provides added security for your Content Gateway system. |
| Retain Client Host Header | When this option is enabled, Content Gateway retains the client host header in a request (it does not include the client host header in the mapping translation). |
| Redirect No-Host Header to URL |
Specifies the alternate URL to which to direct incoming requests from older clients that do not provide a Host: header. It is recommended that you set this option to a page that explains the situation to the user and advises a browser upgrade or provides a link directly to the origin server, bypassing the proxy. Alternatively, you can specify a map rule that maps requests without Host: headers to a particular server. |
| URL Remapping Rules |
Displays a table listing the mapping rules in the remap.config file so that you can redirect HTTP requests permanently or temporarily without the proxy having to contact any origin servers. Note: Mapping a URL to another URL in the same domain requires that a “/” be specified in From Path Prefix field. See the example following this table. |
| Refresh | Updates the table to display the most up-to-date rules in the remap.config file. |
| Edit File | Opens the configuration file editor so that you can edit and add rules to the remap.config file. |
| remap.config Configuration File Editor | |
| rule display box | Lists the remap.config file rules. Select a rule to edit it. The buttons on the left of the box allow you to delete or move the selected rule up or down in the list. |
| Add | Adds a new rule to the rule display box at the top of the configuration file editor page. |
| Set | Updates the rule display box at the top of the configuration file editor page. |
| Rule Type |
Lists the type of rules you can add to the remap.config file: map provides the same function as redirect. Use of redirect is recommended. redirect redirects HTTP requests permanently without having to contact the origin server. Permanent redirects notify the browser of the URL change (by returning an HTTP status code 301) so that the browser can update bookmarks. redirect_temporary redirects HTTP requests temporarily without having to contact the origin server. Temporary redirects notify the browser of the URL change for the current request only (by returning an HTTP status code 307). reverse_map is not supported. |
| From Scheme |
Specifies the protocol of the mapping rule. rtsp and mms are not supported. Note: Mapping a URL of one protocol (scheme) to a different protocol (scheme) is not supported.
|
| From Host | Specifies the hostname of the URL to map from. |
| From Port (Optional) | Specifies the port number in the URL to map from. |
| From Path Prefix (Optional) |
Specifies the path prefix of the URL to map from. Sometimes it is desirable to redirect a URL to a sub-page in the same domain. For example, to redirect “www.cnn.com” to “www.cnn.com/tech”. To make this rule work you must specify “/” in the From Path Prefix field. If it is not specified, the redirection results in a URL that recursively adds the page specifier to the URL. For example, “www.example.com/tech” becomes “www.example.com/tech/tech/tech/tech/tech/tech/tech/tech/...” |
| From Query (Optional) | Specifies the query of the URL to map from. |
| To Scheme | Must match From Scheme. |
| To Host | Specifies the hostname of the URL to map to. |
| To Port (Optional) | Specifies the port number of the URL to map to. |
| To Path Prefix (Optional) | Specifies the path prefix of the URL to map to. |
| To Query (Optional) | Specifies the query of the URL to map to. |
| {undefined} | Specifies the media protocol type of the mapping rule. Not supported. |