This dialog is used to enter Domain-based and Path-based multi-homing options.
Multi-home master
This field displays the name of the multi-homing master. This value can't be changed here
but can be changed by pressing Cancel and selecting another accelerator from the Multi-homing
master list on the previous screen.
DNS name
This field displays the DNS name of the multi-homing master. This value can't be changed here
but can be changed by pressing Cancel and then editing the accelerator on the previous screen.
Multi-homing Options
Two types of multi-homing may be set up via this option: Domain-based and Path-based.
Domain-based multi-homing is used when you want to use the same IP address and port number to
access web servers across different domains. Path-based multi-homing is used when you want to
specify the origin web server based on the path, rather than the DNS name. For example,
http://www.novell.com/web1 and http://www.novell.com/web2 could resolve to different origin web
servers, even though they have the same DNS name. See the iChain* Administration guide for more
details.
Domain-based multi-homing
Selecting this radio button enables Domain-based multi-homing.
DNS name
Enter the DNS name to be used for Domain-based multi-homing in the text field.
Path-based multi-homing
Selecting this radio button enables Path-based multi-homing.
Sub-path match string
This is the portion of the URL after the DNS name that specifies which web server will service the
request. In the example where the URL for the child accelerator is http://www.novell.com/path1,
the sub-path match string is "/path1".
Starts with
Specifies that the sub-path match string should be at the beginning of the path - in other words,
directly after the DNS name in the URL. The configuration above is an example of "Starts with".
Remove sub-path
If "Starts with" is selected, this option will remove the sub-path match string from the URL before
sending the request to the origin web server. If this box is unchecked, the origin web server must
have the requested file in a path matching the sub-path, otherwise the file will not be found.
Ends with
Specifies that the sub-path match string should be at the end of the path. Generally, this would
be a file extension. For example, if a specific web server contained all the JPEG graphics for a
site, you could create a child accelerator with "Ends with" selected and "jpg" as the sub-path
to route all requests with an extension of jpg to that server.
* Novell trademark. ** Third-party trademark. See Legal Notices.