212
Appendix D
Configuration Files
remap.config
The
remap.config
file contains mapping rules that Traffic Server uses to:
•
Map URL requests for a specific origin server to the appropriate location on Traffic Server when Traffic
Server acts as a reverse proxy for that particular origin server
•
Reverse-map server location headers so that when origin servers respond to a request with a location
header that redirects the client to another location, the clients do not bypass the Traffic Server
•
Redirect HTTP requests permanently or temporarily without Traffic Server having to contact any origin
servers
Refer to
Chapter 5‚ Reverse Proxy and HTTP Redirects
for information about redirecting HTTP requests and
using reverse proxy.
Format
Each line in the
remap.config
file must contain a mapping rule. Traffic Server recognizes three space-
delimited fields:
type, target
, and
replacement
. The following table describes the format of each field.
ARM (Security Configuration)
proxy.config.arm.security_enabled
INT
0
Enables (1) or disables (0) ARM security.
Refer to
Controlling host access to the Traffic
Server machine (ARM security)‚ on page 81
.
IMPORTANT
After you modify the
remap.config
file, Traffic Manager has to reread the
configuration files. Run the
traffic_line -x
command. If you are running a cluster,
you need only run the command for one node; the changes will propagate.
Field
Description
type
Enter either one of the following:
map
—translates an incoming request URL to the appropriate origin server URL
(HTTP reverse proxy).
reverse_map
—translates the URL in origin server redirect responses to point to
the Traffic Server (HTTP reverse proxy).
redirect
—redirects HTTP requests permanently without having to contact the
origin server. Permanent redirects notify the browser of the URL change (by
returning an HTTP status code 307) so that the browser can update bookmarks.
redirect_temporary
—redirects HTTP requests temporarily without having to
contact the origin server. Temporary redirects notify the browser of the URL change
for the current request only (by returning an HTTP status code 301).
target
Enter the origin or from URL. You can enter up to four components:
scheme
://
host
:
port
/
path_prefix
replacement
Enter the destination or to URL. You can enter up to four components:
scheme
://
host
:
port
/
path_prefix
Configuration Variable
Data Type
Default Value
Description
