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 2013/04/18 11:57:02 UTC

[18/25] Well what'd ya say. I discovered howto make titles.

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuration-files/remap.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuration-files/remap.config.en.rst b/doc/source/admin/configuration-files/remap.config.en.rst
new file mode 100644
index 0000000..f2887e8
--- /dev/null
+++ b/doc/source/admin/configuration-files/remap.config.en.rst
@@ -0,0 +1,284 @@
+remap.config
+************
+
+.. 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
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+
+
+.. toctree::                                                                                                                                                                                      
+   :maxdepth: 2
+
+
+The ``remap.config`` file contains mapping rules that Traffic Server
+uses to perform the following actions:
+
+-  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 Traffic Server
+-  Redirect HTTP requests permanently or temporarily without Traffic
+   Server having to contact any origin servers
+
+Refer to `Reverse Proxy and HTTP
+Redirects <../reverse-proxy-http-redirects>`_, for information about
+redirecting HTTP requests and using reverse proxy.
+
+**IMPORTANT:** After you modify the ``remap.config`` run the
+``traffic_line -x`` command to apply the changes. When you apply the
+changes to one node in a cluster, Traffic Server automatically applies
+the changes to all other nodes in the cluster.
+
+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 list describes the format
+of each field.
+
+*``type``* {#type}
+    Enter one of the following:
+
+    -  ``map`` --translates an incoming request URL to the appropriate
+       origin server URL.
+
+    -  ``reverse_map`` --translates the URL in origin server redirect
+       responses to point to the Traffic Server.
+
+    -  ``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 301)
+       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 307).
+
+    **Note:** use the ``regex_`` prefix to indicate that the line has a
+    regular expression (regex).
+
+*``target``* {#target}
+    Enter the origin ("from") URL. You can enter up to four components:
+
+    ::
+
+        :::text
+        scheme://host:port/path_prefix
+
+    where *``scheme``* is ``http``.
+
+*``replacement``* {#replacement}
+    Enter the origin ("from") URL. You can enter up to four components:
+
+    ::
+
+        scheme://host:port/path_prefix
+
+    where *``scheme``* can be ``http`` or ``https``.
+
+Precedence
+==========
+
+Remap rules are not processed top-down, but based on an internal
+priority
+
+1. ``map`` and ``reverse_map``
+2. ``redirect`` and ``redirect_temporary``
+3. ``regex_remap``
+4. ``regex_redirect`` and ``regex_redirect_temporary``
+
+Examples
+========
+
+The following section shows example mapping rules in the
+``remap.config`` file.
+
+Reverse Proxy Mapping Rules
+===========================
+
+The following example shows a map rule that does not specify a path
+prefix in the target or replacement:
+
+::
+
+    map http://www.x.com/ http://server.hoster.com/
+    reverse_map http://server.hoster.com/ http://www.x.com/
+
+This rule results in the following translations:
+
+Client Request \| Translated Request
+---------------\|-------------------
+``http://www.x.com/Widgets/index.html`` \|
+``http://server.hoster.com/Widgets/index.html``
+``http://www.x.com/cgi/form/submit.sh?arg=true`` \|
+``http://server.hoster.com/cgi/form/submit.sh?arg=true``
+
+The following example shows a map rule with path prefixes specified in
+the target:
+
+::
+
+    :::text
+    map http://www.y.com/marketing/ http://marketing.y.com/
+    reverse_map http://marketing.y.com/ http://www.y.com/marketing/
+    map http://www.y.com/sales/ http://sales.y.com/
+    reverse_map http://sales.y.com/ http://www.y.com/sales/
+    map http://www.y.com/engineering/ http://engineering.y.com/
+    reverse_map http://engineering.y.com/ http://www.y.com/engineering/
+    map http://www.y.com/stuff/ http://info.y.com/
+    reverse_map http://info.y.com/ http://www.y.com/stuff/
+
+These rules result in the following translations:
+
+Client Request \| Translated Request
+---------------\|-------------------
+``http://www.y.com/marketing/projects/manhattan/specs.html`` \|
+``http://marketing.y.com/projects/manhattan/specs.html``
+``http://www.y.com/stuff/marketing/projects/boston/specs.html`` \|
+``http://info.y.com/marketing/projects/boston/specs.html``
+``http://www.y.com/engineering/marketing/requirements.html`` \|
+``http://engineering.y.com/marketing/requirements.html``
+
+The following example shows that the order of the rules matters:
+
+::
+
+    :::text
+    map http://www.g.com/ http://external.g.com/
+    reverse_map http://external.g.com/ http://www.g.com/
+    map http://www.g.com/stuff/ http://stuff.g.com/
+    reverse_map http://stuff.g.com/ http://www.g.com/stuff/
+
+These rules result in the following translation.
+
+Client Request \| Translated Request
+---------------\|------------------- ``http://www.g.com/stuff/a.gif`` \|
+``http://external.g.com/stuff/a.gif``
+
+In the above examples, the second rule is never applied because all URLs
+that match the second rule also match the first rule. The first rule
+takes precedence because it appears earlier in the ``remap.config``
+file.
+
+The following example shows a mapping with a path prefix specified in
+the target and replacement:
+
+::
+
+    :::text
+    map http://www.h.com/a/b/ http://server.h.com/customers/x/y
+    reverse_map http://server.h.com/customers/x/y/ http://www.h.com/a/b/
+
+This rule results in the following translation.
+
+Client 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``
+
+The following example shows reverse-map rules:
+
+::
+
+    :::text
+    map http://www.x.com/ http://server.hoster.com/x/
+    reverse_map http://server.hoster.com/x/ http://www.x.com/
+
+These rules result in the following translations.
+
+Client Request \| Translated Request
+---------------\|------------------- ``http://www.x.com/Widgets`` \|
+``http://server.hoster.com/x/Widgets`` \|
+
+ 
+
+Client Request \| Origin server Header \| Translated Header
+---------------\|----------------------\|-------------------
+``http://www.x.com/Widgets`` \| ``http://server.hoster.com/x/Widgets/``
+\| ``http://www.x.com/Widgets/``
+
+When acting as a reverse proxy for multiple servers, Traffic Server is
+unable to route to URLs from older browsers that do not send the
+``Host:`` header. As a solution, set the variable
+*``proxy.config.header.parse.no_host_url_redirect``* in the
+``records.config`` file to the URL to which Traffic Server will redirect
+requests without host headers.
+
+Redirect Mapping Rules
+======================
+
+The following rule permanently redirects all HTTP requests for
+``www.company.com`` to ``www.company2.com``:
+
+::
+
+    redirect http://www.company.com/ http://www.company2.com/
+
+The following rule *temporarily* redirects all HTTP requests for
+``www.company1.com`` to ``www.company2.com``:
+
+::
+
+    redirect_temporary http://www.company1.com/ http://www.company2.com/
+
+Regular Expression (regex) Remap Support
+========================================
+
+Regular expressions can be specified in remapping rules, with the
+limitations below:
+
+-  Only the ``host`` field can contain a regex; the ``scheme``,
+   ``port``, and other fields cannot. For path manipulation via regexes,
+   use the ``regex_remap`` plugin.
+-  The number of capturing subpatterns is limited to 9. This means that
+   ``$0`` through ``$9`` can be used as subtraction placeholders (``$0``
+   will be the entire input string).
+-  The number of substitutions in the expansion string is limited to 10.
+-  There is no ``regex_`` equivalent to ``reverse_remap``, so when using
+   ``regex_remap`` you should make sure the reverse path is clear by
+   setting
+   (`*``proxy.config.url_remap.pristine_host_hdr``* <../configuration-files/records.config#proxy.config.url_remap.pristine_host_hdr>`_)
+
+Examples
+--------
+
+::
+
+    regex_map http://x([0-9]+).z.com/ http://real-x$1.z.com/
+    regex_redirect http://old.(.*).z.com http://new.$1.z.com
+
+Plugin Chaining
+===============
+
+Plugins can be configured to be evaluated in a specific order, passing
+the results from one in to the next (unless a plugin returns 0, then the
+"chain" is broken).
+
+Examples
+--------
+
+::
+
+    map http://url/path http://url/path @plugin=/etc/traffic_server/config/plugins/plugin1.so @pparam=1 @pparam=2 @plugin=/etc/traffic_server/config/plugins/plugin2.so @pparam=3
+
+will pass "1" and "2" to plugin1.so and "3" to plugin2.so.
+
+This will pass "1" and "2" to plugin1.so and "3" to plugin2.so

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuration-files/splitdns.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuration-files/splitdns.config.en.rst b/doc/source/admin/configuration-files/splitdns.config.en.rst
new file mode 100644
index 0000000..e1e9013
--- /dev/null
+++ b/doc/source/admin/configuration-files/splitdns.config.en.rst
@@ -0,0 +1,124 @@
+splitdns.config
+***************
+
+.. 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
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+
+
+The ``splitdns.config`` file enables you to specify the DNS server that
+Traffic Server should use for resolving hosts under specific conditions.
+For more information, refer to `Configuring DNS Server Selection (Split
+DNS) <../security-options#SplitDNS>`_.
+
+To specify a DNS server, you must supply the following information in
+each active line within the file:
+
+-  A primary destination specifier in the form of a destination domain,
+   a destination host, or a URL regular expression
+-  A set of server directives, listing one or more DNS servers with
+   corresponding port numbers
+
+You can also include the following optional information with each DNS
+server specification:
+
+-  A default domain for resolving hosts
+-  A search list specifying the domain search order when multiple
+   domains are specified
+
+**IMPORTANT:** After you modify the ``splitdns.config`` file, navigate
+to the Traffic Server\ ``bin`` directory and run the ``traffic_line -x``
+command to apply the changes. When you apply changes to a node in a
+cluster, Traffic Server automatically applies the changes to all other
+nodes in the cluster.
+
+Format
+======
+
+Each line in the ``splitdns.config`` file uses one of the following
+formats:
+
+::
+
+    dest_domain=dest_domain | dest_host | url_regex named=dns_server def_domain=def_domain search_list=search_list
+
+The following list describes each field.
+
+*``dest_domain``* {#dest_domain}
+    A valid domain name. This specifies that DNS server selection will
+    be based on the destination domain. You can prefix the domain with
+    an exclamation mark (``!``) to indicate the NOT logical operator.
+
+*``dest_host``* {#dest_host}
+    A valid hostname. This specifies that DNS server selection will be
+    based on the destination host. You can prefix the host with an
+    exclamation mark (``!``) to indicate the ``NOT`` logical operator.
+
+*``url_regex``* {#url_regex}
+    A valid URL regular expression. This specifies that DNS server
+    selection will be based on a regular expression.
+
+*``dns_server``* {#dns_server}
+    This is a required directive. It identifies the DNS server that
+    Traffic Server should use with the given destination specifier. You
+    can specify a port using a colon (``:``). If you do not specify a
+    port, then 53 is used. Specify multiple DNS servers with spaces or
+    semicolons (``;``) as separators.
+
+    You must specify the domains with IP addresses in CIDR ("dot")
+    notation.
+
+*``def_domain``* {#def_domain}
+    A valid domain name. This optional directive specifies the default
+    domain name to use for resolving hosts. Only one entry is allowed.
+    If you do not provide the default domain, the system determines its
+    value from ``/etc/resolv.conf``
+
+*``search_list``* {#search_list}
+    A list of domains separated by spaces or semicolons (;). This
+    specifies the domain search order. If you do not provide the search
+    list, the system determines the value from ``/etc/resolv.conf``
+
+Examples
+========
+
+Consider the following DNS server selection specifications:
+
+::
+
+      dest_domain=internal.company.com named=255.255.255.255:212 255.255.255.254 def_domain=company.com search_list=company.com company1.com
+      dest_domain=!internal.company.com named=255.255.255.253
+
+Now consider the following two requests:
+
+::
+
+     http://minstar.internal.company.com
+
+This request matches the first line and therefore selects DNS server
+``255.255.255.255`` on port ``212``. All resolver requests use
+``company.com`` as the default domain, and ``company.com`` and
+``company1.com`` as the set of domains to search first.
+
+::
+
+     http://www.microsoft.com
+
+This request matches the second line. Therefore, Traffic Server selects
+DNS server ``255.255.255.253``. Because no ``def_domain`` or
+``search_list`` was supplied, Traffic Server retrieves this information
+from ``/etc/resolv.conf``
+

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuration-files/ssl_multicert.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuration-files/ssl_multicert.config.en.rst b/doc/source/admin/configuration-files/ssl_multicert.config.en.rst
new file mode 100644
index 0000000..7aea5e9
--- /dev/null
+++ b/doc/source/admin/configuration-files/ssl_multicert.config.en.rst
@@ -0,0 +1,78 @@
+ssl_multicert.config
+********************
+
+.. 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
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+
+The ``ssl_multicert.config`` file lets you configure Traffic Server to
+use multiple SSL server certificates with the SSL termination option. If
+you have a Traffic Server system with more than one IP address assigned
+to it, then you can assign a different SSL certificate to be served when
+a client requests a particular IP address.
+
+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 ,
+*``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
+========
+
+The following example configures Traffic Server to use the SSL
+certificate ``server.pem`` for all requests to the IP address
+111.11.11.1 and the SSL certificate ``server1.pem`` for all requests to
+the IP address 11.1.1.1. Since the private key *is* included in the
+certificate files, no private key name is specified.
+
+::
+
+    dest_ip=111.11.11.1  ssl_cert_name=server.pem
+    dest_ip=11.1.1.1   ssl_cert_name=server1.pem
+
+The following example configures Traffic Server to use the SSL
+certificate ``server.pem`` and the private key ``serverKey.pem`` for all
+requests to the IP address 111.11.11.1. Traffic Server uses the SSL
+certificate ``server1.pem`` and the private key ``serverKey1.pem`` for
+all requests to the IP address 11.1.1.1.
+
+::
+
+     dest_ip=111.11.11.1 ssl_cert_name=server.pem ssl_key_name=serverKey.pem
+     dest_ip=11.1.1.1 ssl_cert_name=server1.pem ssl_key_name=serverKey1.pem
+

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuration-files/storage.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuration-files/storage.config.en.rst b/doc/source/admin/configuration-files/storage.config.en.rst
new file mode 100644
index 0000000..a4ff601
--- /dev/null
+++ b/doc/source/admin/configuration-files/storage.config.en.rst
@@ -0,0 +1,132 @@
+storage.config
+**************
+
+.. 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
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+
+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 
+======
+
+The format of the ``storage.config`` file is:
+
+::
+
+    pathname size
+
+where *``pathname``* is the name of a partition, directory or file, and
+*``size``* is the size of the named partition, directory or file (in
+bytes). You must specify a size for directories or files; size is
+optional for raw partitions.
+
+You can use any partition of any size. For best performance:
+
+-  Use raw disk partitions.
+-  For each disk, make all partitions the same size.
+-  For each node, use the same number of partitions on all disks.
+
+Specify pathnames according to your operating system requirements. See
+the following examples. In the ``storage.config`` file, a formatted or
+raw disk must be at least 128 MB.
+
+When using raw disk or partitions, you should make sure the admin user,
+which is the traffic_server running at, have the read&write privileges.
+The admin user_id is set in
+```proxy.config.admin.user_id`` <records.config#proxy.config.admin.user_id>`_.
+One good practice is if the disk set with g+rw, put the admin user into
+the group which have the privileges.
+
+Examples
+========
+
+The following basic example shows 64 MB of cache storage in the
+``/big_dir`` directory:
+
+::
+
+    /big_dir 67108864
+
+You can use the ``.`` symbol for the current directory. Here is an
+example for 64 MB of cache storage in the current directory:
+
+::
+
+    . 67108864
+
+Solaris Example
+---------------
+
+The following example is for the Solaris operating system:
+
+::
+
+    /dev/rdsk/c0t0d0s5
+    /dev/rdsk/c0t0d1s5
+
+**Note:** Size is optional. If not specified, the entire partition is
+used.
+
+Linux Example
+-------------
+
+The following example will use an entire raw disk in the Linux operating
+system:
+
+::
+
+    /dev/sde
+    /dev/sdf
+
+In order to make sure ``traffic_server`` will have access to this disk
+you can use ``udev`` to persistently set the right permissions. The
+following rules are targeted for an Ubuntu system, and stored in
+``/etc/udev/rules.d/51-cache-disk.rules``:
+
+::
+
+    # Assign /dev/sde and /dev/sdf to the www group
+    # make the assignment final, no later changes allowed to the group!
+    SUBSYSTEM=="block", KERNEL=="sd[ef]", GROUP:="www"
+
+FreeBSD Example ## {#LinuxExample}
+----------------------------------
+
+Starting with 5.1 FreeBSD dropped support for explicit raw devices. All
+devices on FreeBSD can be accessed raw now.
+
+The following example will use an entire raw disk in the FreeBSD
+operating system:
+
+::
+
+    :::text
+    /dev/ada1
+    /dev/ada2
+
+In order to make sure ``traffic_server`` will have access to this disk
+you can use ``devfs`` to persistently set the right permissions. The
+following rules are stored in ``/etc/devfs.conf``:
+
+::
+
+    :::text
+    # Assign /dev/ada1 and /dev/ada2 to the tserver user
+    own    ada[12]  tserver:tserver
+

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuration-files/update.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuration-files/update.config.en.rst b/doc/source/admin/configuration-files/update.config.en.rst
new file mode 100644
index 0000000..cbe9d19
--- /dev/null
+++ b/doc/source/admin/configuration-files/update.config.en.rst
@@ -0,0 +1,200 @@
+update.config
+*************
+
+.. 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
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+
+The ``update.config`` file controls how Traffic Server performs a
+scheduled update of specific local cache content. The file contains a
+list of URLs specifying objects that you want to schedule for update.
+
+A scheduled update performs a local HTTP ``GET`` on the objects at the
+specific time or interval. You can control the following parameters for
+each specified object:
+
+-  The URL
+-  URL-specific request headers, which overrides the default
+-  The update time and interval
+-  The recursion depth
+
+**IMPORTANT:** After you modify the ``update.config`` file, navigate to
+the Traffic Serve ``bin`` directory and run the ``traffic_line -x``
+command to apply changes. When you apply changes to one node in a
+cluster, Traffic Server automatically applies the changes to all other
+nodes in the cluster.
+
+Supported Tag/Attribute Pairs
+=============================
+
+Scheduled update supports the following tag/attribute pairs when
+performing recursive URL updates:
+
+-  ``<a href=" ">``
+-  ``<img src=" ">``
+-  ``<img href=" ">``
+-  ``<body background=" ">``
+-  ``<frame src=" ">``
+-  ``<iframe src=" ">``
+-  ``<fig src=" ">``
+-  ``<overlay src=" ">``
+-  ``<applet code=" ">``
+-  ``<script src=" ">``
+-  ``<embed src=" ">``
+-  ``<bgsound src=" ">``
+-  ``<area href=" ">``
+-  ``<base href=" ">``
+-  ``<meta content=" ">``
+
+Scheduled update is designed to operate on URL sets consisting of
+hundreds of input URLs (expanded to thousands when recursive URLs are
+included); it is *not* intended to operate on extremely large URL sets,
+such as those used by Internet crawlers.
+
+Format
+======
+
+Each line in the ``update.config`` file uses the following format:
+
+::
+
+    URL\request_headers\offset_hour\interval\recursion_depth\
+
+The following list describes each field.
+
+*``URL``* {#URL}
+    HTTP-based URLs.
+
+*``request_headers``* {#request_headers}
+    Optional. A list of headers, separated by semicolons, passed in each
+    ``GET`` request. You can define any request header that conforms to
+    the HTTP specification; the default is no request header.
+
+*``offset_hour``* {#offset_hour}
+    The base hour used to derive the update periods. The range is 00-23
+    hours.
+
+*``interval``* {#interval}
+    The interval (in seconds) at which updates should occur, starting at
+    the offset hour.
+
+*``recursion_depth``* {#recursion_depth}
+    The depth to which referenced URLs are recursively updated, starting
+    at the given URL. This field applies only to HTTP.
+
+Examples
+========
+
+An example HTTP scheduled update is provided below:
+
+::
+
+    http://www.company.com\User-Agent: noname user agent\13\3600\5\
+
+The example specifies the URL and request headers, an offset hour of 13
+(1 pm), an interval of one hour, and a recursion depth of 5. This would
+result in updates at 13:00, 14:00, 15:00, and so on. To schedule an
+update that occurs only once a day, use an interval value 86400 (i.e.,
+24 hours x 60 minutes x 60 seconds = 86400).
+
+Specifying URL Regular Expressions (``url_regex``)
+==================================================
+
+This section describes how to specify a ``url_regex``. Entries of type
+``url_regex`` within the configuration files use regular expressions to
+perform a match.
+
+The following list provides examples to show how to create a valid
+``url_regex``.
+
+``x``
+    Matches the character ``x``
+
+``.``
+    Match any character
+
+``^``
+    Specifies beginning of line
+
+``$``
+    Specifies end of line
+
+``[xyz]``
+    A **character class**. In this case, the pattern matches either
+    ``x``, ``y``, or\ ``z``
+
+``[abj-oZ]``
+    A **character class** with a range. This pattern matches ``a``,
+    ``b``, any letter from ``j`` through ``o``, or ``Z``
+
+``[^A-Z]``
+    A **negated character class**. For example, this pattern matches any
+    character except those in the class.
+
+``r*``
+    Zero or more ``r``, where ``r`` is any regular expression.
+
+``r+``
+    One or more ``r``, where ``r`` is any regular expression.
+
+``r?``
+    Zero or one ``r``, where ``r`` is any regular expression.
+
+``r{2,5}``
+    From two to five ``r``, where ``r`` is any regular expression.
+
+``r{2,}``
+    Two or more ``r``, where ``r`` is any regular expression.
+
+``r{4}``
+    Exactly four ``r``, where ``r`` is any regular expression.
+
+``"[xyz]\"images"``
+    The literal string ``[xyz]"images"``
+
+``\X``
+    If ``X`` is ``a, b, f, n, r, t,`` or ``v``, then the ``ANSI-C``
+    interpretation of ``\x``; otherwise, a literal ``X``. This is used
+    to escape operators such as ``*``
+
+``\0``
+    A ``NULL`` character
+
+``\123``
+    The character with octal value ``123``
+
+``\x2a``
+    The character with hexadecimal value ``2a``
+
+``(r)``
+    Matches an ``r``, where ``r`` is any regular expression. You can use
+    parentheses to override precedence.
+
+``rs``
+    The regular expression ``r``, followed by the regular expression
+    ``s``
+
+``r|s``
+    Either an ``r`` or an ``s``
+
+``#<n>#``
+    Inserts an **end node**, which causes regular expression matching to
+    stop when reached. The value ``n`` is returned.
+
+You can specify ``dest_domain=mydomain.com`` to match any host in
+``mydomain.com``. Likewise, you can specify ``dest_domain=.`` to match
+any request.
+

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuration-files/volume.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuration-files/volume.config.en.rst b/doc/source/admin/configuration-files/volume.config.en.rst
new file mode 100644
index 0000000..89d22c5
--- /dev/null
+++ b/doc/source/admin/configuration-files/volume.config.en.rst
@@ -0,0 +1,72 @@
+volume.config
+*************
+
+.. 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
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+
+.. toctree::                                                                                                                                                                                      
+   :maxdepth: 2
+
+The ``volume.config`` file enables you to manage your cache space more
+efficiently and restrict disk usage by creating cache volumes of
+different sizes for specific protocols. You can further configure these
+volumes to store data from certain origin servers and/or domains in the
+`hosting.config <hosting.config>`_ file.
+
+**IMPORTANT:** The volume configuration must be the same on all nodes in
+a cluster. You must stop Traffic Server before you change the cache
+volume size and protocol assignment. For step-by-step instructions about
+partitioning the cache, refer to `Partitioning the
+Cache <../configuring-cache#PartitioningCache>`_.
+
+Format
+======
+
+For each volume you want to create, enter a line with the following
+format:
+
+::
+
+    volume=volume_number  scheme=protocol_type  size=volume_size
+
+where *``volume_number``* is a number between 1 and 255 (the maximum
+number of volumes is 255) and *``protocol_type``* is ``http``. Traffic
+Server supports ``http`` for HTTP volume types; *``volume_size``* is the
+amount of cache space allocated to the volume. This value can be either
+a percentage of the total cache space or an absolute value. The absolute
+value must be a multiple of 128 MB, where 128 MB is the smallest value.
+If you specify a percentage, then the size is rounded down to the
+closest multiple of 128 MB.
+
+Each volume is striped across several disks to achieve parallel I/O. For
+example: if there are four disks, then a 1-GB volume will have 256 MB on
+each disk (assuming each disk has enough free space available). If you
+do not allocate all the disk space in the cache, then the extra disk
+space is not used. You can use the extra space later to create new
+volumes without deleting and clearing the existing volumes.
+
+Examples
+========
+
+The following example partitions the cache evenly between HTTP and HTTPS
+requests:
+
+::
+
+    volume=1 scheme=http size=50%
+    volume=2 scheme=https size=50%
+

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuring-cache.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuring-cache.en.rst b/doc/source/admin/configuring-cache.en.rst
index edf1e8e..72ed7a1 100644
--- a/doc/source/admin/configuring-cache.en.rst
+++ b/doc/source/admin/configuring-cache.en.rst
@@ -1,4 +1,5 @@
-:title: Configuring the Cache
+Configuring the Cache
+*********************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/configuring-traffic-server.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuring-traffic-server.en.rst b/doc/source/admin/configuring-traffic-server.en.rst
index c68f213..3afc8bb 100644
--- a/doc/source/admin/configuring-traffic-server.en.rst
+++ b/doc/source/admin/configuring-traffic-server.en.rst
@@ -1,4 +1,5 @@
-:title: Configuring Traffic Server Notice: Licensed to the Apache
+Configuring Traffic Server
+**************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/event-logging-formats.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/event-logging-formats.en.rst b/doc/source/admin/event-logging-formats.en.rst
index 74240eb..72980ac 100644
--- a/doc/source/admin/event-logging-formats.en.rst
+++ b/doc/source/admin/event-logging-formats.en.rst
@@ -1,4 +1,5 @@
-:title: Event Logging Formats
+Event Logging Formats
+*********************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/explicit-proxy-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/explicit-proxy-caching.en.rst b/doc/source/admin/explicit-proxy-caching.en.rst
index b708d17..7eb61cc 100644
--- a/doc/source/admin/explicit-proxy-caching.en.rst
+++ b/doc/source/admin/explicit-proxy-caching.en.rst
@@ -1,4 +1,5 @@
-:title: Explicit Proxy Caching
+Explicit Proxy Caching
+**********************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/faqs.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/faqs.en.rst b/doc/source/admin/faqs.en.rst
new file mode 100644
index 0000000..8755306
--- /dev/null
+++ b/doc/source/admin/faqs.en.rst
@@ -0,0 +1,408 @@
+FAQ and Troubleshooting Tips
+****************************
+
+.. 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
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+ 
+   http://www.apache.org/licenses/LICENSE-2.0
+ 
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+
+.. toctree::
+   :maxdepth: 2
+
+FAQs
+====
+
+How do you create a raw disk for the cache if all your disks have mounted file systems?
+---------------------------------------------------------------------------------------
+
+Create a large file on filesystem (with ``dd``) and mount it as loopback device.
+This is accomplished with ``loosetup(8)`` on Linux, ``lofiadm(1m)`` on Solaris
+and Illumos, and ``mdconfig(8)`` on FreeBSD.
+
+How do disk I/O errors affect the cache and what does Traffic Server do when a cache disk fails?
+------------------------------------------------------------------------------------------------
+
+If a disk drive fails five successive I/O operations, then Traffic
+Server considers the drive inaccessible and removes the entire disk from
+the cache. Normal cache operations continue for all other Traffic Server
+disk drives.
+
+If a client disconnects during the time that Traffic Server is downloading a large object, is any of the object saved in the cache?
+-----------------------------------------------------------------------------------------------------------------------------------
+
+When a client disconnects during an HTTP operation, Traffic Server
+continues to download the object from the origin server for up to 10
+seconds. If the transfer from the origin server completes successfully
+within 10 seconds after the client disconnect, then Traffic Server
+stores the object in cache. If the origin server download does *not*
+complete successfully within 10 seconds, then Traffic Server disconnects
+from the origin server and deletes the object from cache. Traffic Server
+does not store partial documents in the cache.
+
+Can Traffic Server cache Java applets, JavaScript programs, or other application files like VBScript?
+-----------------------------------------------------------------------------------------------------
+
+Yes, Traffic Server can store and serve Java applets, JavaScript
+programs, VBScripts, and other executable objects from its cache
+according to the freshness and cacheability rules for HTTP objects.
+Traffic Server does not execute the applets, scripts, or programs,
+however - these objects run only when the client system (ie, the one
+that sent the request) loads them.
+
+How do you apply changes to the ``logs_xml.config`` file to all nodes in a cluster?
+-----------------------------------------------------------------------------------
+
+Link to documentation
+
+In Squid- and Netscape-format log files, what do the cache result codes mean?
+-----------------------------------------------------------------------------
+
+This is described in detail in the `Squid log format
+documentation <../working-log-files/squid-format>`_
+
+What is recorded by the ``cqtx`` field in a custom log file?
+------------------------------------------------------------
+
+-  In **forward proxy mode**, the cqtx field records the complete client
+   request in the log file (for example, GET http://www.company.com
+   HTTP/1.0 ).
+-  In **reverse proxy mode**, the cqtx field records the hostname or IP
+   address of the origin server because Traffic Server first remaps the
+   request as per map rules in the
+   `remap.config <../configuration-files/remap.config>`_ file.
+
+Does Traffic Server refresh entries in its host database after a certain period of time if they have not been used?
+-------------------------------------------------------------------------------------------------------------------
+
+By default, the Traffic Server host database observes the time-to-live
+(``ttl``) values set by name servers. You can reconfigure Traffic Server
+to ignore the ``ttl`` set by name servers and use a specific Traffic
+Server setting instead. Alternatively, you can configure Traffic Server
+to compare the ``ttl`` value set by the name server with the ``ttl``
+value set by Traffic Server, and then use either the lower or the higher
+value.
+
+see
+`proxy.config.hostdb.ttl_mode <../configuration-files/records.config#proxy.config.hostdb.ttl_mode>`_
+for more info
+
+Can you improve the look of your custom response pages by using images, animated .gifs, and Java applets?
+---------------------------------------------------------------------------------------------------------
+
+No, because Traffic Server can only respond to clients with a single
+text or HTML document. As a workaround, however, you can provide
+references on your custom response pages to images, animated .gifs, Java
+applets, or objects other than text which are located on a web server.
+Add links in the body_factory template files in the same way you would
+for any image in an HTML document (i.e., with the full URL in the
+``SRC`` attribute).
+
+Can Traffic Server run in forward proxy and reverse proxy modes at the same time?
+---------------------------------------------------------------------------------
+
+Yes. When you enable reverse proxy mode, Traffic Server remaps incoming
+requests according to the map rules in the
+```remap.config`` <../configuration-files/remap.config>`_ file. All
+other requests that do not match a map rule are simply served in forward
+proxy mode.
+
+If you want to run in reverse proxy only mode (wherein Traffic Server
+does *not* serve requests that fail to match a map rule), then you must
+set the configuration variable
+`proxy.config.url_remap.remap_required <../configuration-files/records.config#proxy.config.url_remap.remap_required>`_
+to ``1`` in the
+```records.config`` <../configuration-files/records.config>`_ file.
+
+How do I enable forward proxy mode
+----------------------------------
+
+Please refer to the `Forward Proxy <../forward-proxy>`_ documentation
+
+How do I interpret the Via: header code?
+----------------------------------------
+
+Take a look at our `Via decoder Ring </tools/via>`_
+
+Support for HTTP Expect: Header
+-------------------------------
+
+Traffic Server currently does not handle request Expect: headers
+according to the HTTP/1.1 spec.
+
+Note that clients such as cURL automatically send Expect: for POST
+requests with large POST bodies, with a 1 second timeout if a 100
+Continue response is not received. To avoid the timeout when using cURL
+as a client to Traffic Server, you can turn off the Expect: header as
+follows:
+
+command line:
+
+::
+    curl -H"Expect:" http://www.example.com/
+
+C (libcurl):
+
+::
+    struct curl_slist *header_list=NULL;
+    header_list = curl_slist_append(header_list, "Expect:");
+    curl_easy_setopt(my_curlp, CURLOPT_HTTPHEADER, header_list);
+
+php:
+
+::
+    curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
+
+Troubleshooting Tips
+====================
+
+The throughput statistic is inaccurate
+--------------------------------------
+
+Traffic Server updates the throughput statistic after it has transferred
+an entire object. For larger files, the byte count increases sharply at
+the end of a transfer. The complete number of bytes transferred is
+attributed to the last 10-second interval, although it can take several
+minutes to transfer the object. This inaccuracy is more noticeable with
+a light load. A heavier load yields a more accurate statistic.
+
+You are unable to execute Traffic Line commands
+-----------------------------------------------
+
+Traffic Line commands do not execute under the following conditions:
+
+-  **When the ``traffic_manager`` process is not running** Check to see
+   if the ``**traffic_manager**`` process is running by entering the
+   following command: ``ps aux | grep traffic_manager``
+
+If the ``traffic_manager`` process is not running, then enter the
+following command from the Traffic Server ``bin`` directory to start it:
+``./traffic_manager``
+
+You should always start and stop Traffic Server with the
+``start_traffic_server``\ and ``stop_traffic_server`` commands to ensure
+that all the processes start and stop correctly. For more information,
+refer to `Getting Started <getstart.htm>`_. \* \* **When you are not
+executing the command from ``$TSHome/bin``** If the Traffic Server
+``bin`` directory is not in your path, then prepend the Traffic Line
+commands with ``./`` (for example, ``./traffic_line -h``). \* \* *\*
+When multiple Traffic Server installations are present and you are not
+executing the Traffic Line command from the active Traffic Server path
+specified in ``/etc/trafficserver``*\ \*
+
+You observe inconsistent behavior when one node obtains an object from another node in the cluster
+--------------------------------------------------------------------------------------------------
+
+As part of the initial system preparation, you must synchronize the
+clocks on all nodes in your cluster. Minor time differences do not cause
+problems, but differences of more than a few minutes can affect Traffic
+Server operation.
+
+You should run a clock synchronization daemon such as xntpd. To obtain
+the latest version of xntpd, go to ``http://www.eecis.udel.edu/~ntp/``
+
+Web browsers display an error document with a 'data missing' message
+--------------------------------------------------------------------
+
+A message similar to the following might display in web browsers:
+
+::
+      Data Missing
+
+      This document resulted from a POST operation and has expired from the cache. You can repost the form data to recreate the document by pressing the Reload button.
+
+This is a Web browser issue and not a problem specific to (or caused by)
+Traffic Server. Because Web browsers maintain a separate local cache in
+memory and/or disk on the client system, messages about documents that
+have expired from cache refer to the browser's local cache and _not _
+to the Traffic Server cache. There is no Traffic Server message or
+condition that can cause such messages to appear in a web browser.
+
+Traffic Server does not resolve any websites
+--------------------------------------------
+
+The browser indicates that it is contacting the host and then times out
+with the following message:
+
+::
+        The document contains no data; Try again later, or contact the server's Administrator...
+
+Make sure the system is configured correctly and that Traffic Server can
+read the name resolution file:
+
+-  Check if the server can resolve DNS lookups by issuing the nslookup
+   command (for example, ``nslookup www.myhost.com``).
+-  Check if the ``/etc/resolv.conf`` file contains valid IP addresses
+   for your DNS servers.
+-  On some systems, if the ``/etc/resolv.conf`` file is unreadable or
+   has no name server entry, then the operating system uses
+   ``localhost`` as a name server. Traffic Server, however, does not use
+   this convention. If you want to use ``localhost`` as a name server,
+   then you must add a name server entry for ``127.0.0.1`` or
+   ``0.0.0.0`` in the ``/etc/resolv.conf`` file.
+-  Check that the Traffic Server user account has permission to read the
+   /etc/resolv.conf file. If it does not, then change the file
+   permissions to ``rw-r--r--`` (``644``)
+
+'Maximum document size exceeded' message in the system log file
+---------------------------------------------------------------
+
+The following message appears in the system log file:
+
+::
+         WARNING: Maximum document size exceeded
+
+A requested object was larger than the maximum size allowed in the
+Traffic Server cache, so Traffic Server provided proxy service for the
+oversized object but did not cache it. To set the object size limit for
+the cache, modify the proxy.config.cache.limits.http.max_doc_size
+variable in the records.config file. If you do not want to limit the
+size of objects in the cache, then set the document size
+to\ ``**0**``\ (zero).
+
+'DrainIncomingChannel' message in the system log file
+-----------------------------------------------------
+
+The following messages may appear in the system log file:
+
+::
+     Feb 20 23:53:40 louis traffic_manager[4414]: ERROR ==> [drainIncomingChannel] Unknown message: 'GET http://www.telechamada.pt/ HTTP/1.0'
+     Feb 20 23:53:46 louis last message repeated 1 time 
+     Feb 20 23:53:58 louis traffic_manager[4414]: ERROR ==> [drainIncomingChannel] Unknown message: 'GET http://www.ip.pt/ HTTP/1.0'
+
+These error messages indicate that a browser is sending HTTP requests to
+one of the Traffic Server cluster ports - either ``rsport`` (default
+port 8088) or ``mcport`` (default port 8089). Traffic Server discards
+the request; this error does not cause any Traffic Server problems. The
+misconfigured browser must be reconfigured to use the correct proxy
+port. Traffic Server clusters work best when configured to use a
+separate network interface and cluster on a private subnet, so that
+client machines have no access to the cluster ports.
+
+'No cop file' message in the system log file
+--------------------------------------------
+
+The following message appears repeatedly in the system log file:
+
+::
+     traffic_cop[16056]: encountered "config/internal/no_cop" file...exiting
+
+The file ``config/internal/no_cop`` acts as an administrative control
+that instructs the ``traffic_cop`` process to exit immediately without
+starting ``traffic_manager`` or performing any health checks. The
+``no_cop`` file prevents Traffic Server from starting automatically when
+it has been stopped with the ``stop_traffic_server`` command. Without
+this static control, Traffic Server would restart automatically upon
+system reboot. The ``no_cop`` control keeps Traffic Server off until it
+is explicitly restarted with the
+
+::
+    trafficserver start
+
+command.
+
+
+Warning in the system log file when manually editing vaddrs.config
+------------------------------------------------------------------
+
+If you manually edit the vaddrs.config file as a non-root user, then
+Traffic Server issues a warning message in the system log file similar
+to the following:
+
+::
+         WARNING: interface is ignored: Operation not permitted
+
+You can safely ignore this message; Traffic Server *does* apply your
+configuration edits.
+
+Traffic Server is running but no log files are created
+------------------------------------------------------
+
+Traffic Server only writes event log files when there is information to
+record. If Traffic Server is idle, then it's possible/probable that no
+log files exist. In addition:
+
+Make sure you're looking in the correct directory. By default, Traffic
+Server creates log files in the logs directory. Check the location of
+log files by checking the value of the variable
+proxy.config.log.logfile_dir in the records.config file. Check that the
+log directory has read/write permissions for the Traffic Server user
+account. If the log directory does not have the correct permissions,
+then the traffic_server process is unable to open or create log files.
+Check that logging is enabled by checking the value of the
+proxy.config.log.logging_enabled variable in the records.config file.
+Check that a log format is enabled. In the records.config file, select
+the standard or custom format by editing variables in the Logging Config
+section.
+
+Traffic Server shows an error indicating too many network connections
+---------------------------------------------------------------------
+
+By default, Traffic Server supports 8000 network connections: half of
+this number is allocated for client connections and the remaining half
+is for origin server connections. A **connection throttle event** occurs
+when client or origin server connections reach 90% of half the
+configured limit (3600 by default). When a connection throttle event
+occurs, Traffic Server continues processing all existing connections but
+will not accept new client connection requests until the connection
+count falls below the limit.
+
+Connection throttle events can occur under the following conditions:
+
+-  If there is a **connection spike** (e.g., if thousands of client
+   requests all reach Traffic Server at the same time). Such events are
+   typically transient and require no corrective action.
+-  If there is a **service overload** (e.g., if client requests
+   continuously arrive faster than Traffic Server can service them).
+   Service overloads often indicate network problems between Traffic
+   Server and origin servers. Conversely, it may indicate that Traffic
+   Server needs more memory, CPU, cache disks, or other resources to
+   handle the client load.
+
+If necessary, you can reset the maximum number of connections supported
+by Traffic Server by editing the value of the
+``_proxy.config.net.connections_throttle _`` configuration variable in
+the records.config file. Do not increase the connection throttle limit
+unless the system has adequate memory to handle the client connections
+required. A system with limited RAM might need a throttle limit lower
+than the default value. Do not set this variable below the minimum value
+of 100.
+
+Low memory symptoms
+-------------------
+
+Under heavy load, the Linux kernel can run out of RAM. This low memory
+condition can cause slow performance and a variety of other system
+problems. In fact, RAM exhaustion can occur even if the system has
+plenty of free swap space.
+
+Symptoms of extreme memory exhaustion include the following messages in
+the system log files (``/var/log/messages``):
+
+::
+     WARNING: errno 105 is ENOBUFS (low on kernel memory), consider a memory upgrade `kernel: eth0: can't fill rx buffer (force 0)!
+     kernel: recvmsg bug: copied E01BA916 seq E01BAB22
+
+To avoid memory exhaustion, add more RAM to the system or reduce the
+load on Traffic Server.
+
+Connection timeouts with the origin server
+------------------------------------------
+
+Certain origin servers take longer than 30 seconds to post HTTP
+requests, which results in connection timeouts with Traffic Server. To
+prevent such connection timeouts, you must change the value of the
+configuration variable proxy.config.http.connect_attempts_timeout in
+the records.config file to 60 seconds or more.
+

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/forward-proxy.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/forward-proxy.en.rst b/doc/source/admin/forward-proxy.en.rst
index 1b6c35f..00b4e91 100644
--- a/doc/source/admin/forward-proxy.en.rst
+++ b/doc/source/admin/forward-proxy.en.rst
@@ -1,4 +1,5 @@
-:title: Forward Proxy
+Forward Proxy
+*************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
@@ -49,8 +50,8 @@ be pointed to the more dynamic
 This port will then serve a JavaScript like configuration that User
 Agents can use to determine where to send their requests to.
 
-Configuration # {#configuration}
-================================
+Configuration
+=============
 
 In order to configure Apache Traffic Server as forward proxy you will
 have to edit

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/getting-started.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/getting-started.en.rst b/doc/source/admin/getting-started.en.rst
index 97b3828..6a15fef 100644
--- a/doc/source/admin/getting-started.en.rst
+++ b/doc/source/admin/getting-started.en.rst
@@ -1,4 +1,5 @@
-:title: Getting Started
+Getting Started
+***************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/hierachical-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/hierachical-caching.en.rst b/doc/source/admin/hierachical-caching.en.rst
index 4571f85..beaf6f7 100644
--- a/doc/source/admin/hierachical-caching.en.rst
+++ b/doc/source/admin/hierachical-caching.en.rst
@@ -1,4 +1,5 @@
-:itle: Hierarchical Caching
+Hierarchical Caching
+********************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/http-proxy-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/http-proxy-caching.en.rst b/doc/source/admin/http-proxy-caching.en.rst
index 0db4520..3a9fc14 100644
--- a/doc/source/admin/http-proxy-caching.en.rst
+++ b/doc/source/admin/http-proxy-caching.en.rst
@@ -1,4 +1,5 @@
-:title: HTTP Proxy Caching Notice: Licensed to the Apache Software
+HTTP Proxy Caching
+******************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/index.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/index.en.rst b/doc/source/admin/index.en.rst
index d1f693f..3032832 100644
--- a/doc/source/admin/index.en.rst
+++ b/doc/source/admin/index.en.rst
@@ -1,4 +1,5 @@
-:title: Apache Traffic Server Title: Administrators's Guide - Overview
+Apache Traffic Server Title: Administrators's Guide - Overview
+**************************************************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/monitoring-traffic.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/monitoring-traffic.en.rst b/doc/source/admin/monitoring-traffic.en.rst
index 141f853..f5af50e 100644
--- a/doc/source/admin/monitoring-traffic.en.rst
+++ b/doc/source/admin/monitoring-traffic.en.rst
@@ -1,4 +1,5 @@
-:title: Monitoring Traffic
+Monitoring Traffic
+******************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins.en.rst b/doc/source/admin/plugins.en.rst
index ada02a2..c82bf9f 100644
--- a/doc/source/admin/plugins.en.rst
+++ b/doc/source/admin/plugins.en.rst
@@ -1,4 +1,5 @@
-:title: Apache Traffic Server Plugins
+Apache Traffic Server Plugins
+*****************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
@@ -58,8 +59,8 @@ Most plugins can be build by simply issueing
 in their source tree. Note that this requires you to have ``tsxs`` in
 your ``PATH``
 
-Plugins # {#plugins}
-====================
+Plugins
+=======
 
 .. toctree::
    :maxdepth: 2

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/balancer.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/balancer.en.rst b/doc/source/admin/plugins/balancer.en.rst
index 80ca31b..9d54d91 100644
--- a/doc/source/admin/plugins/balancer.en.rst
+++ b/doc/source/admin/plugins/balancer.en.rst
@@ -1,4 +1,5 @@
-:title: Balancer Plugin
+Balancer Plugin
+***************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/buffer_upload.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/buffer_upload.en.rst b/doc/source/admin/plugins/buffer_upload.en.rst
index 0f81239..ab5f209 100644
--- a/doc/source/admin/plugins/buffer_upload.en.rst
+++ b/doc/source/admin/plugins/buffer_upload.en.rst
@@ -1,4 +1,5 @@
-:title: Buffer Upload Plugin
+Buffer Upload Plugin
+********************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/cacheurl.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/cacheurl.en.rst b/doc/source/admin/plugins/cacheurl.en.rst
index 89e6968..0bda6e9 100644
--- a/doc/source/admin/plugins/cacheurl.en.rst
+++ b/doc/source/admin/plugins/cacheurl.en.rst
@@ -1,4 +1,5 @@
-:title: CacheURL Plugin
+CacheURL Plugin
+***************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
@@ -25,8 +26,8 @@ request.
 It is designed so that multiple requests that have different URLs but
 the same content (for example, site mirrors) need be cached only once.
 
-Installation # {#Installation}
-==============================
+Installation
+============
 
 ::
     make
@@ -39,8 +40,8 @@ will need to specify the path to tsxs manually:
     make TSXS=/opt/ts/bin/tsxs
     sudo make TSXS=/opt/ts/bin/tsxs install
 
-Configuration # {#Configuration}
-================================
+Configuration
+=============
 
 Create a ``cacheurl.config`` file in the plugin directory with the url
 patterns to match. See the ``cacheurl.config.example`` file for what to

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/combo_handler.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/combo_handler.en.rst b/doc/source/admin/plugins/combo_handler.en.rst
index 84497bb..11e4633 100644
--- a/doc/source/admin/plugins/combo_handler.en.rst
+++ b/doc/source/admin/plugins/combo_handler.en.rst
@@ -1,4 +1,5 @@
-:title: Combohandler Plugin
+Combohandler Plugin
+*******************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/esi.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/esi.en.rst b/doc/source/admin/plugins/esi.en.rst
index 6e6bde3..9130791 100644
--- a/doc/source/admin/plugins/esi.en.rst
+++ b/doc/source/admin/plugins/esi.en.rst
@@ -1,5 +1,5 @@
-:title: ESI Notice: Licensed to the
-:title: Apache Traffic Server Plugins
+ESI Plugin (undocumented)
+*************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/geoip_acl.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/geoip_acl.en.rst b/doc/source/admin/plugins/geoip_acl.en.rst
index 876b562..774c146 100644
--- a/doc/source/admin/plugins/geoip_acl.en.rst
+++ b/doc/source/admin/plugins/geoip_acl.en.rst
@@ -1,4 +1,6 @@
-:title: GeoIP ACLs Plugin
+GeoIP ACLs Plugin
+*****************
+
 .. 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

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/gzip.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/gzip.en.rst b/doc/source/admin/plugins/gzip.en.rst
index bfe8627..d601f0d 100644
--- a/doc/source/admin/plugins/gzip.en.rst
+++ b/doc/source/admin/plugins/gzip.en.rst
@@ -1,4 +1,5 @@
-:title: gzip / deflate Plugin
+gzip / deflate Plugin
+*********************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
@@ -21,8 +22,8 @@
 This plugin gzips or deflates responses, whichever is applicable. It can
 compress origin respones as well as cached responses.
 
-Installation # {#Installation}
-==============================
+Installation
+============
 
 First, run:
 

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/header_filter.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/header_filter.en.rst b/doc/source/admin/plugins/header_filter.en.rst
index d81cfe1..755a458 100644
--- a/doc/source/admin/plugins/header_filter.en.rst
+++ b/doc/source/admin/plugins/header_filter.en.rst
@@ -1,4 +1,5 @@
-:title: Header Filter Plugin
+Header Filter Plugin
+********************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/hipes.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/hipes.en.rst b/doc/source/admin/plugins/hipes.en.rst
index a5fd44f..2651c67 100644
--- a/doc/source/admin/plugins/hipes.en.rst
+++ b/doc/source/admin/plugins/hipes.en.rst
@@ -1,5 +1,5 @@
-:title: HIPES system (undocumented)
-:title: Apache Traffic Server Plugins
+HIPES system (undocumented)
+***************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
@@ -21,8 +21,8 @@
 
 This plugin implements the HIPES system.
 
-Configuration # {#Configuration}
-================================
+Configuration
+=============
 
 ``server:<host>``
     Name of the server to send this request to

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/mysql_remap.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/mysql_remap.en.rst b/doc/source/admin/plugins/mysql_remap.en.rst
index 8a4cfd9..671e83b 100644
--- a/doc/source/admin/plugins/mysql_remap.en.rst
+++ b/doc/source/admin/plugins/mysql_remap.en.rst
@@ -1,4 +1,5 @@
-:title: MySQL Remap Plugin
+MySQL Remap Plugin
+******************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/regex_remap.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/regex_remap.en.rst b/doc/source/admin/plugins/regex_remap.en.rst
index 3f10849..b486eec 100644
--- a/doc/source/admin/plugins/regex_remap.en.rst
+++ b/doc/source/admin/plugins/regex_remap.en.rst
@@ -1,4 +1,5 @@
-:title: Regex Remap Plugin
+Regex Remap Plugin
+******************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/stale_while_revalidate.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/stale_while_revalidate.en.rst b/doc/source/admin/plugins/stale_while_revalidate.en.rst
index 411d3be..0a59c90 100644
--- a/doc/source/admin/plugins/stale_while_revalidate.en.rst
+++ b/doc/source/admin/plugins/stale_while_revalidate.en.rst
@@ -1,4 +1,5 @@
-:title: Stale While Revalidate Plugin (undocumented)
+Stale While Revalidate Plugin (undocumented)
+********************************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/plugins/stats_over_http.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/plugins/stats_over_http.en.rst b/doc/source/admin/plugins/stats_over_http.en.rst
index 4b317f4..95ffb49 100644
--- a/doc/source/admin/plugins/stats_over_http.en.rst
+++ b/doc/source/admin/plugins/stats_over_http.en.rst
@@ -1,4 +1,5 @@
-:title: Stats over HTTP Plugin
+Stats over HTTP Plugin (underdocumented)
+****************************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/reverse-proxy-http-redirects.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/reverse-proxy-http-redirects.en.rst b/doc/source/admin/reverse-proxy-http-redirects.en.rst
index a4921f5..27db562 100644
--- a/doc/source/admin/reverse-proxy-http-redirects.en.rst
+++ b/doc/source/admin/reverse-proxy-http-redirects.en.rst
@@ -1,4 +1,5 @@
-:title: Reverse Proxy and HTTP Redirects
+Reverse Proxy and HTTP Redirects
+********************************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/57464fbd/doc/source/admin/security-options.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/security-options.en.rst b/doc/source/admin/security-options.en.rst
index b12dcd1..88b933c 100644
--- a/doc/source/admin/security-options.en.rst
+++ b/doc/source/admin/security-options.en.rst
@@ -1,4 +1,5 @@
-:title: Security Options Notice: Licensed to the Apache Software
+Security Options
+****************
 
 .. Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file