134 Intel NetStructure Cache Appliance Administrator’s Guide
In these examples, the second rule is never applied because all URL addresses
that match the second rule also match the first rule. The first rule takes
precedence because it appears earlier in the remap.config file.
Example 4 A mapping with a path prefix specified in the target and replacement:
This rule results in the following translation:
Example 5 Reverse mapping:
These rules result in the following translations:
For
browsers that
do not support
host headers
When accelerating multiple servers, the appliance is unable to route to URL
addresses from older browsers that do not send the Host: header. The best
solution is to direct the user to a page that explains the situation and advises a
browser upgrade or provides a link directly to the origin server, bypassing the
appliance. For information on how to do this, see Setting server accelerator
options‚ on page 43.
map http://www.h.com/a/b http://server.h.com/customers/x/y
User Request Translated Request
http://www.h.com/a/b/c/d/
doc.html
http://server.h.com/customers/x/y/c/d/
doc.html
http://www.h.com/a/index.html Translation fails
map http://www.x.com/ http://server.hoster.com/x/
reverse_map http://server.hoster.com/x/ http://www.x.com/
User Request Translated Request
http://www.x.com/
Widgets
http://server.hoster.com/x/Widgets
User Request Origin Server Header Translated Header
http://www.x.com/
Widgets
http://server.hoster.com/
x/Widgets/
http://www.x.com/
Widgets/