131
Appendix B
Traffic Manager Configuration Options
The Protocols page
The following table describes the configuration options on the Protocols page.
Control customizable response
pages:
Select Turn Off Customizable Response Pages to send the default
response pages to clients.
Select Enable Default Custom Response Pages to send customized
response pages to your clients. You can customize the error message
text and format to provide a different look and feel or to explain the
errors in a different language.
Select Enable Language-Targeted Custom Response Pages to
send the customized response pages to clients in the language
specified in the Accept-Language header.
Select Log Customization Activity to Error Log to send a message
to the error log each time a customized response page is used or
modified.
Control Response Page Template
Directory
Specifies the directory where customized response page templates
reside. The default is Traffic Server’s
c
onfig/body_factory
directory.
Option
Definition
HTTP
Keep-Alive Timeout Inbound
Specifies how long the Traffic Server should keep connections to
clients open for a subsequent request after a transaction ends. Each
time the Traffic Server opens a connection to accept a client request,
it handles the request, then keeps the connection alive for the timeout
period you specify. If the client does not make another request before
the timeout expires, the Traffic Server closes the connection. If the
client does make another request, the timeout period starts over.
NOTE:
The client can close the connection at any time.
Keep-Alive Timeout Outbound
Specifies how long the Traffic Server should keep connections to
origin servers open for a subsequent transfer of data after a
transaction ends. Each time the Traffic Server opens a connection to
download data from an origin server, it downloads the data, then
keeps the connection alive for the timeout period you specify. If the
Traffic Server does not need to make a subsequent request for data
before the timeout expires, it closes the connection. If it does, the
timeout period starts over.
NOTE:
The origin server can close the connection at any time.
Inactivity Timeout Inbound
Specifies how long the Traffic Server should keep connections to
clients open if a transaction stalls. If the Traffic Server stops
receiving data from a client or the client stops reading the data, the
Traffic Server closes the connection when this timeout expires.
NOTE:
The client can close the connection at any time.
Inactivity Timeout Outbound
Specifies how long the Traffic Server should keep connections to
origin servers open if the transaction stalls. If the Traffic Server stops
receiving data from an origin server, it will not close the connection
until this timeout has expired.
NOTE:
The origin server can close the connection at any time.