You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ig...@apache.org on 2011/11/15 23:23:28 UTC
svn commit: r1202446 - in
/trafficserver/site/branches/ats-cms/content/docs/trunk/admin:
cluster-howto/ configuration-files/
Author: igalic
Date: Tue Nov 15 22:23:27 2011
New Revision: 1202446
URL: http://svn.apache.org/viewvc?rev=1202446&view=rev
Log:
Fix titles, so they don't always contain "Configuration Files",
that looks tedious in the Navigation.
Once that's done, why not also remove the first h1, which is again
a repitition? And why not also move the whole structure one <hX> level up?
Yeah, let's do that. Also: Candy.
Modified:
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/bypass.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/cache.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/congestion.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/icp.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ip_allow.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/log_hosts.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/parent.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/remap.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/splitdns.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ssl_multicert.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/storage.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/update.config.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Traffic Serverâ¢
+Title: Traffic Server Cluster
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -18,15 +18,13 @@ Notice: Licensed to the Apache Softwa
Navigation: [*](*)
-# Traffic Server Cluster
-
Traffic Server scales from a single node to multiple nodes that form a
cluster allowing you to improve system performance and reliability. This
chapter discusses the following topics:
[TOC](#toc)
-## Understanding Traffic Server Clusters ## {#UnderstandingTSClusters}
+# Understanding Traffic Server Clusters # {#UnderstandingTSClusters}
A Traffic Server cluster consists of multiple Traffic Server nodes. The
nodes in a cluster share configuration information and can form a single
@@ -40,7 +38,7 @@ cluster. Traffic Server has two clusteri
* Full-clustering mode; refer to Full Clustering
-### Management-Only Clustering ### {#ManagementOnlyClustering}
+# Management-Only Clustering # {#ManagementOnlyClustering}
In management-only clustering mode, Traffic Server cluster nodes share
configuration information. You can administer all the nodes at the same
@@ -51,7 +49,7 @@ nodes, and the `traffic_manager` process
configuration changes to all the nodes.
-### Full Clustering ### {#FullClustering}
+# Full Clustering # {#FullClustering}
In full-clustering mode, as well as sharing configuration information, a
Traffic Server cluster distributes its cache across its nodes into a
@@ -74,7 +72,7 @@ Full clustering recommends a dedicated n
communication to get better performance.
-## Enable Clustering Mode ## {#EnableClusteringMode}
+# Enable Clustering Mode # {#EnableClusteringMode}
Before you put a node into a Cluster, please make sure the following thing
checked:
@@ -119,7 +117,7 @@ After a successful join of the cluster,
node, will take effect on **all** node now.
-## Deleting Nodes from a Cluster ## {#DeletingNodesFromCluster}
+# Deleting Nodes from a Cluster # {#DeletingNodesFromCluster}
To delete a node from the Traffic Server cluster, just roll back
`proxy.config.cluster.type` to the default value 3 and reload.
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/bypass.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/bypass.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/bypass.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/bypass.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - bypass.config
+Title: bypass.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# bypass.config ## {#bypass.config}
The bypass.config file contains static bypass rules that Traffic Server
uses in transparent proxy caching mode. Static bypass rules instruct
@@ -52,7 +51,7 @@ You can configure three types of static
Traffic Server.
-### Format ### {#Format}
+# Format # {#Format}
Bypass rules follow the format below:
@@ -89,7 +88,7 @@ The following list describes the variabl
The variable ipaddress must be a single IP address, such as 123.45.67.8
-### Dynamic Deny Bypass Rules ### {#DynamicDenyBypassRules}
+# Dynamic Deny Bypass Rules # {#DynamicDenyBypassRules}
In addition to static bypass rules, the bypass.config file also accepts
dynamic deny bypass rules that prevent Traffic Server from bypassing
@@ -110,7 +109,7 @@ static bypass rule and a dynamic bypass
then the dynamic deny bypass rule will be ignored.
-### Examples ###
+# Examples #
The following example shows source, destination, and source/destination
**bypass rules**:
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/cache.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/cache.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/cache.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/cache.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - cache.config
+Title: cache.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,8 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# cache.config # {#cache.config}
-
The cache.config file defines how Traffic Server caches web objects. You
can add caching rules to specify the following:
- Not to cache objects from specific IP addresses
@@ -32,7 +30,7 @@ changes. When you apply the changes to a
automatically applies the changes to all other nodes in the cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the cache.config file contains a caching rule. Traffic Server
recognizes three space-delimited tags:
@@ -119,7 +117,7 @@ The following list shows possible action
pin-in-cache and revalidate .
-### Examples ### {#Examples}
+# Examples # {#Examples}
The following example configures Traffic Server to revalidate `gif` and `jpeg`
objects in the domain `mydomain.com` every 6 hours, and all other objects in
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/congestion.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/congestion.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/congestion.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/congestion.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - congestion.config
+Title: congestion.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# congestion.config # {#congestion.config}
The `congestion.config` file enables you to configure Traffic Server to stop
forwarding HTTP requests to origin servers when they become congested, and
@@ -40,7 +39,7 @@ You can create rules in the congestion.c
hostname.
-## Format ## {#Format}
+# Format # {#Format}
Each line in `congestion.config` must follow the format below. Traffic
Server applies the rules in the order listed, starting at the top of the
@@ -143,7 +142,7 @@ The following list shows the possible ta
congested, then both IP addresses are marked as congested.
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following `congestion.config` rule configures Traffic Server to stop
forwarding requests to the server `www.host.com` on port 80 (HTTP traffic)
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/hosting.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - hosting.config
+Title: hosting.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# hosting.config # {#hosting.config}
The `hosting.config` file enables you to assign cache partitions to specific
origin servers and/or domains so that you can manage cache space
@@ -40,7 +39,7 @@ applies the changes to all other nodes i
cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the `hosting.config` file must have one of the following
formats:
@@ -63,7 +62,7 @@ shown in the example below. The [hosting
cannot contain multiple entries for the same origin server or domain.
-## Generic Partition ## {#GenericPartition}
+# Generic Partition # {#GenericPartition}
When configuring the hosting.config file, you must assign a generic
partition to use for content that does not belong to any of the origin
@@ -78,7 +77,7 @@ The generic partition must have the foll
where `partition_numbers` is a comma-separated list of generic partitions.
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following example configures Traffic Server to store content from the
domain `mydomain.com` in partition 1 and content from `www.myhost.com` in
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/icp.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/icp.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/icp.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/icp.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - icp.config
+Title: icp.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# icp.config # {#icp.config}
The `icp.config` file defines ICP peers (parent and sibling caches).
@@ -27,7 +26,7 @@ changes. When you apply the changes to a
automatically applies the changes to all other nodes in the cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the icp.config file contains the name and configuration
information for a single ICP peer in the following format:
@@ -64,7 +63,7 @@ Each field is described in the following
communication.
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following example configuration is for three nodes: the local host,
one parent, and one sibling.
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/index.en.mdtext Tue Nov 15 22:23:27 2011
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# Configuration Files # {#ConfigurationFiles}
This section describes Traffic Server configuration files that you can edit.
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ip_allow.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ip_allow.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ip_allow.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ip_allow.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - ip_allow.config
+Title: ip_allow.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,8 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# ip_allow.config # {#ip_allow.config}
-
The `ip_allow.config` file controls client access to the Traffic Server
proxy cache. You can specify ranges of IP addresses that are allowed to
use the Traffic Server as a web proxy cache.
@@ -28,7 +26,7 @@ you apply the changes to a node in a clu
applies the changes to all other nodes in the cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the `ip_allow.config` file must have the following format:
@@ -49,7 +47,7 @@ access, comment out or delete this line
src_ip=0.0.0.0-255.255.255.255 action=ip_allow
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following example enables all clients to access the Traffic Server
proxy cache:
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/log_hosts.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/log_hosts.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/log_hosts.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/log_hosts.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - log_hosts.config
+Title: log_hosts.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# log_hosts.config # {#log_hosts.config}
To record HTTP transactions for different origin servers in
separate log files, you must list each origin server hostname in
@@ -31,7 +30,7 @@ changes to a node in a cluster, Traffic
applies the changes to all other nodes in the cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the `log_hosts.config` file has the following format:
@@ -46,7 +45,7 @@ keyword in their names in a separate log
below.
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following example configures Traffic Server to create separate
log files containing all HTTP transactions for the origin servers
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - logs_xml.config
+Title: logs_xml.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -18,14 +18,12 @@ Notice: Licensed to the Apache Softwa
Navigation: [*](*)
-# logs_xml.config # {#logs_xml.config}
-
The `logs_xml.config` file defines the custom log file formats,
filters, and processing options. The format of this file is modeled
after **XML**, the Extensible Markup Language.
-## Format ## {#Format}
+# Format # {#Format}
The `logs_xml.config` file contains the specifications below:
@@ -41,7 +39,7 @@ The `logs_xml.config` file ignores extra
and all comments.
-## LogFormat ## {#LogFormat}
+# LogFormat # {#LogFormat}
The following list shows **`LogFormat`** specifications.
@@ -261,7 +259,7 @@ The following list shows the `LogObject`
: The size at which log files are rolled.
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following is an example of a **`LogFormat`** specification
that collects information using three common fields:
@@ -330,7 +328,7 @@ entries are sent to port 4000 of the col
</LogObject>
-## WELF ## {#WELF}
+# WELF # {#WELF}
Traffic Server supports WELF (WebTrends Enhanced Log Format) so you
can analyze Traffic Server log files with WebTrends reporting
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/parent.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/parent.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/parent.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/parent.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - parent.config
+Title: parent.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# parent.config # {#parent.config}
The `parent.config` file identifies the parent proxies used in an
cache hierarchy. Use this file to perform the following
@@ -38,7 +37,7 @@ node in a cluster, Traffic Server automa
to all other nodes in the cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the `parent.config` file must contain a parent caching
rule. Traffic Server recognizes three space-delimited tags:
@@ -118,7 +117,7 @@ values.
* `false` - requests do not bypass parent hierarchies.
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following rule configures a parent cache hierarchy consisting
of Traffic Server (which is the child) and two parents, `p1.x.com`
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - records.config
+Title: records.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# records.config # {#records.config}
The `records.config` file is a list of configurable variables used
by the Traffic Server software. Many of the variables in the
@@ -29,7 +28,7 @@ apply the changes. When you apply change
Traffic Server automatically applies the changes to all other nodes
in the cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each variable has the following format:
CONFIG variable_name DATATYPE variable_value
@@ -37,7 +36,7 @@ Each variable has the following format:
where `DATATYPE` is `INT` (integer), `STRING` (string), or `FLOAT`
(floating point).
-## Examples ## {#Examples}
+# Examples # {#Examples}
In the following example, the
variable *`proxy.config.proxy_name`* is a `STRING` datatype
@@ -57,13 +56,13 @@ timeout to 10 seconds.
CONFIG proxy.config.cluster.startup_timeout INT 10
-## Configuration Variables ## {#ConfigurationVariables}
+# Configuration Variables # {#ConfigurationVariables}
The following list describes the configuration variables available in
the `records.config` file.
-### System Variables ### {#SystemVariables}
+# System Variables # {#SystemVariables}
*`proxy.config.product_company`* {#proxy.config.product_company}
: `STRING`
@@ -172,7 +171,7 @@ the `records.config` file.
: The new default thread stack size, for all threads. The original default is set at 1 MB.
-### Cluster ### {#Cluster}
+# Cluster # {#Cluster}
*`proxy.local.cluster.type`* {#proxy.local.cluster.type}
: `INT`
@@ -193,7 +192,7 @@ the `records.config` file.
: Default: `1`
: The number of threads for cluster communication. On heavy cluster, the number should be adjusted. It is recommend that take the thread CPU usage as a reference when adjusting.
-### Local Manager ### {#LocalManager}
+# Local Manager # {#LocalManager}
*`proxy.config.lm.sem_id`* {#proxy.config.lm.sem_id}
: `INT`
@@ -225,7 +224,7 @@ the `records.config` file.
Setting `user_id` to `root` or `#0` is now forbidden to increase security. Trying to do so, will cause the `traffic_server` fatal failure. However there are two ways to bypass that restriction: Specify `-DBIG_SECURITY_HOLE` in `CXXFLAGS` during compilation Set the `user_id=#-1` and start trafficserver as root.
-### Process Manager ### {#ProcessManager}
+# Process Manager # {#ProcessManager}
*`proxy.config.process_manager.mgmt_port`* {#proxy.config.process_manager.mgmt_port}
: `INT`
@@ -233,7 +232,7 @@ the `records.config` file.
: The port used for internal communication between the `traffic_manager` and `traffic_server` processes.
-### Alarm Configuration ### {#ProcessManager}
+# Alarm Configuration # {#ProcessManager}
*`proxy.config.alarm.bin`* {#proxy.config.alarm.bin}
: `STRING`
@@ -247,7 +246,7 @@ the `records.config` file.
-### HTTP Engine ### {#HTTPEngine}
+# HTTP Engine # {#HTTPEngine}
*`proxy.config.http.server_port`* {#proxy.config.http.server_port}
: `INT`
@@ -367,7 +366,7 @@ the `records.config` file.
This solution must be considered interim. In the longer term, it should be possible to arrange for much finer grained control of DNS lookup so that wildcard domain can be set to use Traffic Server or client resolution. In both known use cases, marking specific domains as client determined (rather than a single global switch) would suffice. It is possible to do this crudely with this flag by enabling it and then use identity URL mappings to re-disable it for specific domains.
-### Parent Proxy Configuration ### {#ParentProxyConfiguration}
+# Parent Proxy Configuration # {#ParentProxyConfiguration}
*`proxy.config.http.parent_proxy_routing_enable`* {#proxy.config.http.parent_proxy_routing_enable}
: `INT`
@@ -409,7 +408,7 @@ the `records.config` file.
-### HTTP Connection Timeouts ### {#HTTPConnectionTimeouts}
+# HTTP Connection Timeouts # {#HTTPConnectionTimeouts}
*`proxy.config.http.keep_alive_no_activity_timeout_in`* {#proxy.config.http.keep_alive_no_activity_timeout_in}
: `INT`
@@ -460,7 +459,7 @@ the `records.config` file.
: The proportion of total document size already transferred when a client aborts at which the proxy continues fetching the document from the origin server to get it into the cache (a **background fill**).
-### Origin Server Connect Attempts ### {#OriginServerConnectAttempts}
+# Origin Server Connect Attempts # {#OriginServerConnectAttempts}
*`proxy.config.http.connect_attempts_max_retries`* {#proxy.config.http.connect_attempts_max_retries}
: `INT`
@@ -513,7 +512,7 @@ the `records.config` file.
: The number of seconds before Traffic Server marks an origin server as unavailable after a client abandons a request because the origin server was too slow in sending the response header.
-### Congestion Control ### {#CongestionControl}
+# Congestion Control # {#CongestionControl}
*`proxy.config.http.congestion_control.enabled`* {#proxy.config.http.congestion_control.enabled}
: `INT`
@@ -521,7 +520,7 @@ the `records.config` file.
: Enables (`1`) or disables (`0`) the Congestion Control option, which configures Traffic Server to stop forwarding HTTP requests to origin servers when they become congested. Traffic Server sends the client a message to retry the congested origin server later. Refer to [Using Congestion Control](../http-proxy-caching#UsingCongestionControl).
-### Negative Response Caching ### {#NegativeResponseCaching}
+# Negative Response Caching # {#NegativeResponseCaching}
*`proxy.config.http.negative_caching_enabled`* {#proxy.config.http.negative_caching_enabled}
: `INT`
@@ -543,7 +542,7 @@ the `records.config` file.
504 Gateway Timeout
-### Proxy User Variables ### {#ProxyUserVariables}
+# Proxy User Variables # {#ProxyUserVariables}
*`proxy.config.http.anonymize_remove_from`* {#proxy.config.http.anonymize_remove_from}
: `INT`
@@ -602,7 +601,7 @@ the `records.config` file.
This is useful for minimizing cached alternates of documents (e.g. `gzip, deflate` vs. `deflate, gzip`). Enabling this option is recommended if your origin servers use no encodings other than `gzip`.
-### Security ### {#Security}
+# Security # {#Security}
*`proxy.config.http.push_method_enabled`* {#proxy.config.http.push_method_enabled}
: `INT`
@@ -612,7 +611,7 @@ the `records.config` file.
**Important:** If you enable this option, then you must also specify a filtering rule in the [`filter.config`](filter.config) file to allow only certain machines to push content into the cache.
-### Cache Control ### {#CacheControl}
+# Cache Control # {#CacheControl}
*`proxy.config.cache.enable_read_while_writer`* {#proxy.config.cache.enable_read_while_writer}
: `INT`
@@ -774,7 +773,7 @@ the `records.config` file.
: Default: `0`
: When enabled (`1`), Traffic Server will keep certain HTTP objects in the cache for a certain time as specified in [`cache.config`](cache.config).
-### Heuristic Expiration ### {#HeuristicExpiration}
+# Heuristic Expiration # {#HeuristicExpiration}
*`proxy.config.http.cache.heuristic_min_lifetime`* {#proxy.config.http.cache.heuristic_min_lifetime}
: `INT`
@@ -802,7 +801,7 @@ the `records.config` file.
: Default: `0.00500`
: The probability that a refresh is made on a document during the specified fuzz time.
-### Dynamic Content & Content Negotiation ### {#DynamicContentAndContentNegotiation}
+# Dynamic Content & Content Negotiation # {#DynamicContentAndContentNegotiation}
*`proxy.config.http.cache.vary_default_text`* {#proxy.config.http.cache.vary_default_text}
: `STRING`
@@ -821,7 +820,7 @@ the `records.config` file.
: The header on which Traffic Server varies for anything other than text and images.
-### Customizable User Response Pages ### {#CustomizableUserResponsePages}
+# Customizable User Response Pages # {#CustomizableUserResponsePages}
*`proxy.config.body_factory.enable_customizations`* {#proxy.config.body_factory.enable_customizations}
: `INT`
@@ -852,7 +851,7 @@ the `records.config` file.
* `2` = suppress response pages only for intercepted traffic
-### DNS ### {#DNS}
+# DNS # {#DNS}
*`proxy.config.dns.search_default_domains`* {#proxy.config.dns.search_default_domains}
: `INT`
@@ -893,7 +892,7 @@ the `records.config` file.
: Indicates whether to utilize SRV records for orgin server lookup.
-### HostDB ### {#HostDB}
+# HostDB # {#HostDB}
*`proxy.config.hostdb.serve_stale_for`* {#proxy.config.hostdb.serve_stale_for}
: `INT`
@@ -933,7 +932,7 @@ the `records.config` file.
: When disabled (`0`), Traffic Server always uses the same origin server for the same client, for as long as the origin server is available.
-### Logging Config ### {#LoggingConfig}
+# Logging Config # {#LoggingConfig}
*`proxy.config.log.logging_enabled`* {#proxy.config.log.logging_enabled}
: `INT`
@@ -1192,7 +1191,7 @@ the `records.config` file.
: The number of milliseconds before a slow connection's debugging stats are dumped. Specify `1` to enable or `0` to disable.
-### Reverse Proxy ### {#ReverseProxy}
+# Reverse Proxy # {#ReverseProxy}
*`proxy.config.reverse_proxy.enabled`* {#proxy.config.reverse_proxy.enabled}
: `INT`
@@ -1207,7 +1206,7 @@ the `records.config` file.
: The URL to which to redirect requests with no host headers (reverse proxy).
-### URL Remap Rules ### {#URLRemapRules}
+# URL Remap Rules # {#URLRemapRules}
*`proxy.config.url_remap.default_to_server_pac`* {#proxy.config.url_remap.default_to_server_pac}
: `INT`
@@ -1230,7 +1229,7 @@ the `records.config` file.
: Set this variable to `1` if you want to retain the client host header in a request during remapping.
-### SSL Termination ### {#SSLTermination}
+# SSL Termination # {#SSLTermination}
*`proxy.config.ssl.accelerator_required`* {#proxy.config.ssl.accelerator_required}
: `INT`
@@ -1325,7 +1324,7 @@ the `records.config` file.
: The location of the certificate authority file that client certificates will be verified against.
-#### Client-Related Configuration #### {#SSLClientRelatedConfigurations}
+## Client-Related Configuration ## {#SSLClientRelatedConfigurations}
*`proxy.config.ssl.client.verify.server`* {#proxy.config.ssl.client.verify.server}
: `INT`
@@ -1363,7 +1362,7 @@ the `records.config` file.
: Specifies the location of the certificate authority file against which the origin server will be verified.
-### ICP Configuration ### {#ICPConfiguration}
+# ICP Configuration # {#ICPConfiguration}
*`proxy.config.icp.enabled`* {#proxy.config.icp.enabled}
: `INT`
@@ -1394,7 +1393,7 @@ the `records.config` file.
: Specifies the timeout used for ICP queries.
-### Scheduled Update Configuration ### {#ScheduledUpdatesConfiguration}
+# Scheduled Update Configuration # {#ScheduledUpdatesConfiguration}
*`proxy.config.update.enabled`* {#proxy.config.update.enabled}
: `INT`
@@ -1422,7 +1421,7 @@ the `records.config` file.
: Specifies the maximum simultaneous update requests allowed at any time. This option prevents the scheduled update process from overburdening the host.
-### Remap Plugin Processor ### {#RemapPluginProcessor}
+# Remap Plugin Processor # {#RemapPluginProcessor}
*`proxy.config.remap.use_remap_processor`* {#proxy.config.remap.use_remap_processor}
: `INT`
@@ -1435,7 +1434,7 @@ the `records.config` file.
: Specifies the number of threads that will be used for remap plugin processing.
-### Plug-in Configuration ### {#PluginConfiguration}
+# Plug-in Configuration # {#PluginConfiguration}
*`proxy.config.plugin.plugin_dir`* {#proxy.config.plugin.plugin_dir}
: `STRING`
@@ -1443,7 +1442,7 @@ the `records.config` file.
: Specifies the location of Traffic Server plugins.
-### Sockets ### {#Sockets}
+# Sockets # {#Sockets}
*`proxy.config.net.defer_accept`* {#proxy.config.net.defer_accept}
: `INT`
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/remap.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/remap.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/remap.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/remap.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - remap.config
+Title: remap.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,9 +17,7 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-[TOC]
-
-# remap.config # {#remap.config}
+[TOC](#toc)
The `remap.config` file contains mapping rules that Traffic Server
uses to perform the following actions:
@@ -106,7 +104,7 @@ Remap rules are not processed top-down,
The following section shows example mapping rules in the
`remap.config` file.
-## Reverse Proxy Mapping Rules ## {#ReverseProxyMappingRules}
+# Reverse Proxy Mapping Rules # {#ReverseProxyMappingRules}
The following example shows a map rule that does not specify a path
prefix in the target or replacement:
@@ -202,7 +200,7 @@ is unable to route to URLs from older br
redirect requests without host headers.
-## Redirect Mapping Rules ## {#RedirectMappingRules}
+# Redirect Mapping Rules # {#RedirectMappingRules}
The following rule permanently redirects all HTTP requests for
`www.company.com` to `www.company2.com`:
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/splitdns.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/splitdns.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/splitdns.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/splitdns.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - splitdns.config
+Title: splitdns.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# splitdns.config # {#splitdns.config}
The `splitdns.config` file enables you to specify the DNS server
that Traffic Server should use for resolving hosts under specific
@@ -45,7 +44,7 @@ command to apply the changes. When you a
cluster, Traffic Server automatically applies the changes to all
other nodes in the cluster.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the `splitdns.config` file uses one of the following
formats:
@@ -90,7 +89,7 @@ The following list describes each field.
specifies the domain search order. If you do not provide the search
list, the system determines the value from `/etc/resolv.conf`
-## Examples ## {#Examples}
+# Examples # {#Examples}
Consider the following DNS server selection specifications:
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ssl_multicert.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ssl_multicert.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ssl_multicert.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/ssl_multicert.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - ssl_multicert.config
+Title: ssl_multicert.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# ssl_multicert.config # {#ssl_multicert.config}
The `ssl_multicert.config` file lets you configure Traffic Server
to use multiple SSL server certificates with the SSL termination
@@ -26,20 +25,31 @@ address assigned to it, then you can ass
certificate to be served when a client requests a particular IP
address.
-## Format ## {#Format}
+# Format # {#Format}
The format of the `ssl_multicert.config` file is:
dest_ip=ipaddress ssl_cert_name=cert_name ssl_key_name=key_name
where *`ipaddress`* is an IP address assigned to Traffic
-Server , *`cert_name`* is the filename of the Traffic Server
-SSL server certificate, and *`key_name`* is the filename of
+Server , *`ssl_cert_name`* is the filename of the Traffic Server
+SSL server certificate, *`ssl_key_name`* is the filename of
the Traffic Server SSL private key. If the private key is located
in the certificate file, then you do not need to specify the name
of the private key.
+Additionally *`ssl_ca_name`* can be used to specify the location
+of a Certification Authorithy change in case that differs from
+what is specified under [`records.config`](../records.config)'s
+[`proxy.config.ssl.CA.cert.filename`](../records.config#proxy.config.ssl.CA.cert.filename).
+
+Traffic Server will try to find the files specified in *`ssl_cert_name`*
+relative to [`proxy.config.ssl.server.cert.path`](../records.config#proxy.config.ssl.server.cert.path),
+*`ssl_key_name`*
+relative to [`proxy.config.ssl.server.private_key.path`](../records.config#proxy.config.ssl.server.private_key.path),
+and *`ssl_ca_name`* relative to [`proxy.config.ssl.CA.cert.path`](../records.config#proxy.config.ssl.CA.cert.path).
-## Examples ## {#Examples}
+
+# Examples # {#Examples}
The following example configures Traffic Server to use the SSL
certificate `server.pem` for all requests to the IP address
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/storage.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/storage.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/storage.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/storage.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - storage.config
+Title: storage.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,14 +17,13 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# storage.config # {#storage.config}
The `storage.config` file lists all the files, directories, and/or
hard disk partitions that make up the Traffic Server cache. After
you modify the `storage.config` file, you must restart Traffic
Server.
-## Format ## {#Format}
+# Format # {#Format}
The format of the `storage.config` file is:
@@ -46,7 +45,7 @@ Specify pathnames according to your oper
See the following examples. In the `storage.config` file, a
formatted or raw disk must be at least 128 MB.
-## Examples ## {#Examples}
+# Examples # {#Examples}
The following basic example shows 64 MB of cache storage in the
`/big_dir` directory:
@@ -60,7 +59,7 @@ example for 64 MB of cache storage in th
:::text
. 67108864
-### Solaris Example ### {#SolarisExample}
+## Solaris Example ## {#SolarisExample}
The following example is for the Solaris operating system:
@@ -71,7 +70,7 @@ The following example is for the Solaris
**Note:** Size is optional. If not specified, the entire
partition is used.
-### Linux Example ### {#LinuxExample}
+## Linux Example ## {#LinuxExample}
The following example will use an entire raw disk in the Linux operating system:
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/update.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/update.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/update.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/update.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - update.config
+Title: update.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,7 +17,6 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-# update.config # {#update.config}
The `update.config` file controls how Traffic Server performs a
scheduled update of specific local cache content. The file contains
@@ -39,7 +38,7 @@ command to apply changes. When you apply
cluster, Traffic Server automatically applies the changes to all
other nodes in the cluster.
-## Supported Tag/Attribute Pairs ## {#SupportedTagAttributePairs}
+# Supported Tag/Attribute Pairs # {#SupportedTagAttributePairs}
Scheduled update supports the following tag/attribute pairs when
performing recursive URL updates:
@@ -65,7 +64,7 @@ hundreds of input URLs (expanded to thou
are included); it is *not* intended to operate on extremely large
URL sets, such as those used by Internet crawlers.
-## Format ## {#Format}
+# Format # {#Format}
Each line in the `update.config` file uses the following format:
@@ -94,7 +93,7 @@ The following list describes each field.
starting at the given URL. This field applies only to HTTP.
-## Examples ## {#Examples}
+# Examples # {#Examples}
An example HTTP scheduled update is provided below:
@@ -107,7 +106,7 @@ schedule an update that occurs only once
value 86400 (i.e., 24 hours x 60 minutes x 60 seconds = 86400).
-## Specifying URL Regular Expressions (`url_regex`) ## {#URLregex}
+# Specifying URL Regular Expressions (`url_regex`) # {#URLregex}
This section describes how to specify a `url_regex`. Entries of
type `url_regex` within the configuration files use regular
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext?rev=1202446&r1=1202445&r2=1202446&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/volume.config.en.mdtext Tue Nov 15 22:23:27 2011
@@ -1,4 +1,4 @@
-Title: Configuration Files - volume.config
+Title: volume.config
Notice: Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
@@ -17,9 +17,8 @@ Notice: Licensed to the Apache Softwa
under the License.
Navigation: [*](*)
-[TOC]
+[TOC](#toc)
-# volume.config # {#parition.config}
The `volume.config` file enables you to manage your cache space
more efficiently and restrict disk usage by creating cache