Supporting local host traffic in remote device infrastructure
摘要
說(shuō)明書(shū)
The operator of the infrastructure 100 can provide one or more alias URLs with host names that do not match any items on the exclusion list 302, but nevertheless point to the same IP address of an item on the exclusion list 302. For example, the URL request “l(fā)ocalhost,” which may be on the exclusion list 302 points to the IP address “127.0.0.1.” The operator of the infrastructure 100 can provide an alias URL, for example “bs-local.com,” which is not on the exclusion list 302, but points to the same IP address “127.0.0.1.” When the RDB 109 receives the URL request “bs-local.com,” the implicit bypass rules are not triggered and the RDB 109 forwards the request to the proxy server 115 and the remaining operations of the infrastructure 100 proceed as they would for any other URL requests. In this example, the repeater 110 cannot resolve the URL request “bs-local.com,” and forwards it to the REL application 106. The REL application 106 forwards the request to the localhost 301 because the IP address of the domain name or host server “bs-local.com” points to the IP address of the localhost 301.
