When a client tries to access a particular URL, the host name in the URL is matched with the entries in the Proxies for Domains and Subdomains list. The entry that matches the longest suffix of the requested host name is considered. For example, consider that the requested host name is host1.sesta.com
The Proxies for Domains and Subdomains is scanned for host1.sesta.com. If a matching entry is found, the proxy specified against this entry is used to connect to this host.
Else, the list is scanned for *.sesta.com. If an entry is found, the corresponding proxy is used.
Else, the list is searched for sesta.com. If an entry is found, the corresponding proxy is used.
Else, the list is searched for *.com. If an entry is found, the corresponding proxy is used.
Else the list is searched for com. If an entry is found, the corresponding proxy is used.
Else the list is searched for *. If an entry is found, the corresponding proxy is used.
Else, a direct connection is attempted.
Consider the following entries in the Proxies for Domains and Subdomains list:
com p1| host1 p2 | host2 | * p3 sesta.com p4 | host5 p5 | * p6 florizon.com | host6 abc.sesta.com p8 | host7 p7 | host8 p8 | * p9 host6.florizon.com p10 host9.sesta.com p11 siroe.com | host12 p12 | host13 p13 | host14 | * p14 siroe.com | host15 p15 | host16 | * p16 * p17 |
The Gateway internally maps these entries into a table as shown in Processing the Web Proxy Information.
Table 2–2 Mapping of Entries in the Proxies for Domains and Subdomains List
Number |
Entry in Proxies for Domains and Subdomains List |
Proxy |
Description |
---|---|---|---|
1 |
com |
p1 |
As specified in the list. |
2 |
host1.com |
p2 |
As specified in the list. |
3 |
host2.com |
p1 |
The proxy for the domain is used as no proxy is specified against host2. |
4 |
*.com |
p3 |
As specified in the list. |
5 |
sesta.com |
p4 |
As specified in the list. |
6 |
host5.sesta.com |
p5 |
As specified in the list. |
7 |
*.sesta.com |
p6 |
As specified in the list. |
8 |
florizon.com |
Direct |
See the description for entry 14 for details. |
9 |
host6.florizon.com |
– |
See the description for entry 14 for details. |
10 |
abc.sesta.com |
p8 |
As specified in the list. |
11 |
host7.abc.sesta.com |
p7 |
As specified in the list. |
12 |
host8.abc.sesta.com |
p8 |
As specified in the list. |
13 |
*.abc.sesta.com |
p9 |
As specified in the list. For all hosts other than host7 and host8 under the abc.sesta.com domain, p9 is used as the proxy. |
14 |
host6.florizon.com |
p10 |
This entry is the same as entry 9. Entry 9 indicates a direct connection, whereas this entry indicates that proxy p10 should be used. In a case with two entries such as this, the entry with the proxy information is considered as the valid entry. The other entry is ignored. |
15 |
host9.sesta.com |
p11 |
As specified in the list. |
16 |
siroe.com |
Direct |
A direct connection is attempted because no proxy is specified for siroe.com, . |
17 |
host12.siroe.com |
p12 |
As specified in the list. |
18 |
host13.siroe.com |
p13 |
As specified in the list. |
19 |
host14.siroe.com |
Direct |
A direct connection is attempted because no proxy is specified for host14. |
20 |
*.siroe.com |
p14 |
See the description for entry 23. |
21 |
host15.siroe.com |
p15 |
As specified in the list. |
22 |
host16.siroe.com |
Direct |
A direct connection is attempted because no proxy is specified for host16 or siroe.com. |
23 |
*.siroe.com |
p16 |
Similar to entry 20. But the proxies specified are different. In such a case, the exact behavior of the Gateway is not known. Either of the two proxies may be used. |
24 |
* |
p17 |
If no other entry matches the requested URL, p17 is used as the proxy. |
Instead of separating the proxy entries in the Proxies for Domains and Subdomains list with the | symbol, it may be simpler to have individual entries in the list. For example, instead of an entry such as:
sesta.com p1 | red p2 | * p3 |
you can specify it as:
sesta.com p1 red.sesta.com p2 *.sesta.com p3 |
This makes it easier to trap repeated entries or any other ambiguities.