Document routing rewrite rules

Whereas the corresponding proxy request would look like this:

GET http://real.janes_books.com/index.html HTTP/1.0

HOST: real.janes_books.com

The appliance can construct a proxy request from a server request by using the server information in the host header.

You might have noticed a small problem. The correct proxy request must contain the host name of the origin server, not the advertised host name that names servers associated to the appliance. The advertised host name is what appears in the host header. For example, for the origin server real.janes_books.com in Figure 6, the server request and host header would be:

GET /index.html HTTP/1.0

HOST: www.janes_books.com

And the correct proxy request should be:

GET http://real.janes_books.com/index.html HTTP/1.0

HOST: real.janes_books.com

To translate www.janes_books.com to real.janes_books.com, the appliance needs a set of document routing rewrite rules by which it can refer to the full paths on the Web servers it is accelerating. These rules are stored in the remap.config file. In the preceding example, the rule to map www.janes_books.com to real.janes_books.com would be:

map www.janes_books.com real.janes_books.com

Two types of rules exist: map rules and reverse-maprules.

Map rules specify the location of content that the appliance is accelerating; they enable the appliance to translate a URL requested by a client into one that represents the accelerated content.

Reverse-map rules translate origin server redirects to clients. If an origin server sends a redirect response to a client, the appliance translates the redirect so that the client is redirected to the appliance, instead of being redirected around it. For more information on reverse-map rules, see Web server redirects‚ on page 131.

For detailed descriptions of both map rules and reverse-map rules, see Understanding server acceleration mapping rules‚ on page 132 and Examples of rules and translations‚ on page 133.

The map rule for the other Web server illustrated in Figure 6, big.server.net, which hosts jazz.flute.org, might look as follows:

map jazz.flute.org big.server.net/jazz/

130Intel NetStructure Cache Appliance Administrator’s Guide

Page 142
Image 142
Intel 1520 manual Whereas the corresponding proxy request would look like this