trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jpe...@apache.org
Subject [33/51] trafficserver git commit: Documentation reorganization
Date Tue, 03 Nov 2015 06:10:09 GMT
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/admin/configuring-cache.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/configuring-cache.en.rst b/doc/admin/configuring-cache.en.rst
deleted file mode 100644
index 3930ef4..0000000
--- a/doc/admin/configuring-cache.en.rst
+++ /dev/null
@@ -1,424 +0,0 @@
-.. _configuring-the-cache:
-
-Configuring the Cache
-*********************
-
-.. 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 Traffic Server cache consists of a high-speed object database called
-the :term:`object store` that indexes :term:`cache objects <cache object>`
-according to URLs and their associated headers.
-
-.. toctree::
-   :maxdepth: 2
-
-The Traffic Server Cache
-========================
-
-The Traffic Server cache consists of a high-speed object database called
-the :term:`object store`. The object store indexes
-:term:`cache objects <cache object>` according to URLs and associated headers.
-This enables Traffic Server to store, retrieve, and serve not only web pages,
-but also parts of web pages - which provides optimum bandwidth savings. Using
-sophisticated object management, the object store can cache
-:term:`alternate` versions of the same object (versions may differ because of
-dissimilar language or encoding types). It can also efficiently store very
-small and very large documents, thereby minimizing wasted space. When the
-cache is full, Traffic Server removes :term:`stale` data to ensure the most
-requested objects are kept readily available and fresh.
-
-Traffic Server is designed to tolerate total disk failures on any of the
-cache disks. If the disk fails completely, then Traffic Server marks the
-entire disk as corrupt and continues using the remaining disks. An alarm
-is then created to indicate which disk failed. If all of the cache disks
-fail, then Traffic Server goes into proxy-only mode.
-
-You can perform the following cache configuration tasks:
-
--  Change the total amount of disk space allocated to the cache; refer
-   to `Changing Cache Capacity`_.
-
--  Partition the cache by reserving cache disk space for specific
-   protocols and :term:`origin servers/domains <origin server>`; refer to
-   `Partitioning the Cache`_.
-
--  Delete all data in the cache; refer to `Clearing the Cache`_.
-
--  Override cache directives for a requested domain name, regex on a url,
-   hostname or ip, with extra filters for time, port, method of the request,
-   and more. ATS can be configured to never cache, always cache,
-   ignore no-cache directives, etc. These are configured in :file:`cache.config`.
-
-The RAM Cache
-=============
-
-Traffic Server maintains a small RAM cache of extremely popular objects.
-This RAM cache serves the most popular objects as quickly as possible
-and reduces load on disks, especially during temporary traffic peaks.
-You can configure the RAM cache size to suit your needs, as described in
-:ref:`changing-the-size-of-the-ram-cache` below.
-
-The RAM cache supports two cache eviction algorithms, a regular *LRU*
-(Least Recently Used) and the more advanced *CLFUS* (Clocked Least
-Frequently Used by Size; which balances recentness, frequency, and size
-to maximize hit rate, similar to a most frequently used algorithm).
-The default is to use *CLFUS*, and this is controlled via
-:ts:cv:`proxy.config.cache.ram_cache.algorithm`.
-
-Both the *LRU* and *CLFUS* RAM caches support a configuration to increase
-scan resistance. In a typical *LRU*, if you request all possible objects in
-sequence, you will effectively churn the cache on every request. The option
-:ts:cv:`proxy.config.cache.ram_cache.use_seen_filter` can be set to add some
-resistance against this problem.
-
-In addition, *CLFUS* also supports compressing in the RAM cache itself.
-This can be useful for content which is not compressed by itself (e.g.
-images). This should not be confused with ``Content-Encoding: gzip``, this
-feature is only present to save space internally in the RAM cache itself. As
-such, it is completely transparent to the User-Agent. The RAM cache
-compression is enabled with the option
-:ts:cv:`proxy.config.cache.ram_cache.compress`.
-
-Possible values are:
-
-======= =============================
-Value   Meaning
-======= =============================
-0       No compression (*default*)
-1       *fastlz* compression
-2       *libz* compression
-3       *liblzma* compression
-======= =============================
-
-.. _changing-the-size-of-the-ram-cache:
-
-Changing the Size of the RAM Cache
-==================================
-
-Traffic Server provides a dedicated RAM cache for fast retrieval of
-popular small objects. The default RAM cache size is automatically
-calculated based on the number and size of the
-:term:`cache partitions <cache partition>` you have configured. If you've
-partitioned your cache according to protocol and/or hosts, then the size of
-the RAM cache for each partition is proportional to the size of that partition.
-
-You can increase the RAM cache size for better cache hit performance.
-However, if you increase the size of the RAM cache and observe a
-decrease in performance (such as increased latencies), then it's
-possible that the operating system requires more memory for network
-resources. In such instances, you should return the RAM cache size to
-its previous value.
-
-To change the RAM cache size:
-
-#. Stop Traffic Server.
-
-#. Set the variable :ts:cv:`proxy.config.cache.ram_cache.size`
-   to specify the size of the RAM cache. The default value of ``-1`` means
-   that the RAM cache is automatically sized at approximately 1MB per
-   gigabyte of disk.
-
-#. Restart Traffic Server. If you increase the RAM cache to a size of
-   1GB or more, then restart with the :program:`trafficserver` command
-   (refer to :ref:`start-traffic-server`).
-
-Changing Cache Capacity
-=======================
-
-You can increase or reduce the total amount of disk space allocated to
-the cache without clearing the content. To check the size of the cache
-(in bytes), enter the command :option:`traffic_ctl metric get`
-``proxy.process.cache.bytes_total``.
-
-Increasing Cache Capacity
--------------------------
-
-To increase the total amount of disk space allocated to the cache on
-existing disks, or to add new disks to a Traffic Server node:
-
-#. Stop Traffic Server.
-
-#. Add hardware, if necessary.
-
-#. Edit :file:`storage.config` to increase the amount of disk space allocated
-   to the cache on existing disks or describe the new hardware you are adding.
-
-#. Restart Traffic Server.
-
-Reducing Cache Capacity
------------------------
-
-To reduce the total amount of disk space allocated to the cache on an
-existing disk, or to remove disks from a Traffic Server node:
-
-#. Stop Traffic Server.
-
-#. Remove hardware, if necessary.
-
-#. Edit :file:`storage.config` to reduce the amount of disk space allocated
-   to the cache on existing disks or delete the reference to the hardware you're removing.
-
-#. Restart Traffic Server.
-
-.. important:: In :file:`storage.config`, a formatted or raw disk must be at least 128 MB.
-
-.. _partitioning-the-cache:
-
-Partitioning the Cache
-======================
-
-You can manage your cache space more efficiently and restrict disk usage
-by creating :term:`cache volumes <cache volume>` with different sizes for
-specific protocols. You can further configure these volumes to store data from
-specific :term:`origin servers <origin server>` and/or domains. The volume
-configuration must be the same on all nodes in a :ref:`cluster <traffic-server-cluster>`.
-
-Creating Cache Partitions for Specific Protocols
-------------------------------------------------
-
-You can create separate :term:`volumes <cache volume>` for your cache that vary
-in size to store content according to protocol. This ensures that a certain
-amount of disk space is always available for a particular protocol. Traffic
-Server currently supports only the ``http`` partition type.
-
-To partition the cache according to protocol:
-
-#. Enter a line in :file:`volume.config` for each volume you want to create. ::
-
-    volume=1 scheme=http size=50%
-    volume=2 scheme=http size=50%
-
-#. Restart Traffic Server.
-
-.. important::
-
-    Volume definitions must be the same across all nodes in a cluster.
-
-Making Changes to Partition Sizes and Protocols
------------------------------------------------
-
-After you've configured your cache volumes based on protocol, you can
-make changes to the configuration at any time. Before making changes,
-note the following:
-
--  You must stop Traffic Server before you change the cache volume size
-   and protocol assignment.
-
--  When you increase the size of a volume, the contents of the volume
-   are *not* deleted. However, when you reduce the size of a volume, the
-   contents of the volume *are* deleted.
-
--  When you change the volume number, the volume is deleted and then
-   recreated, even if the size and protocol type remain the same.
-
--  When you add new disks to your Traffic Server node, volume sizes
-   specified in percentages will increase proportionately.
-
--  Substantial changes to volume sizes can result in disk fragmentation,
-   which affects performance and cache hit rate. You should clear the cache
-   before making many changes to cache volume sizes (refer to `Clearing the Cache`_).
-
-Partitioning the Cache According to Origin Server or Domain
------------------------------------------------------------
-
-.. XXX: rewrite to remove repetitious single-v-multiple points; break out global partition note for clarify; fix up plurality
-
-After you have partitioned the cache according to size and protocol, you
-can assign the volumes you created to specific origin servers and/or
-domains. You can assign a volume to a single origin server or to
-multiple origin servers. However, if a volume is assigned to multiple
-origin servers, then there is no guarantee on the space available in the
-volumes for each origin server. Content is stored in the volumes
-according to popularity. In addition to assigning volumes to specific
-origin servers and domains, you must assign a generic volume to store
-content from all origin servers and domains that are not listed. This
-generic volume is also used if the partitions for a particular origin
-server or domain become corrupt. If you do not assign a generic volume,
-then Traffic Server will run in proxy-only mode.
-
-.. note::
-
-    You do not need to stop Traffic Server before you assign volumes
-    to particular hosts or domains. However, this type of configuration
-    is time-consuming and can cause a spike in memory usage.
-    Therefore, it's best to configure partition assignment during
-    periods of low traffic.
-
-To partition the cache according to hostname and domain:
-
-#. Configure the cache volumes according to size and protocol, as
-   described in `Creating Cache Partitions for Specific Protocols`_.
-#. Create a separate volume based on protocol for each host and domain,
-   as well as an additional generic partition to use for content that
-   does not belong to these origin servers or domains. The volumes do
-   not need to be the same size.
-#. Enter a line in the :file:`hosting.config` file to
-   allocate the volume(s) used for each origin server and/or domain.
-#. Assign a generic volume to use for content that does not belong to
-   any of the origin servers or domains listed in the file. If all
-   volumes for a particular origin server become corrupt, then Traffic
-   Server will also use the generic volume to store content for that
-   origin server as per :file:`hosting.config`.
-#. Run the command :option:`traffic_ctl config reload` to apply the configuration
-   changes.
-
-Configuring the Cache Object Size Limit
-=======================================
-
-By default, Traffic Server allows objects of any size to be cached. You
-can change the default behavior and specify a size limit for objects in
-the cache via the steps below:
-
-#. Set :ts:cv:`proxy.config.cache.max_doc_size`
-   to specify the maximum size in bytes allowed for objects in the cache.
-   A setting of ``0`` (zero) will permit cache objects to be unlimited in size.
-#. Run the command :option:`traffic_ctl config reload` to apply the configuration
-   changes.
-
-.. _clearing-the-cache:
-
-Clearing the Cache
-==================
-
-When you clear the cache, you remove all data from the entire cache -
-including data in the host database. You should clear the cache before
-performing certain cache configuration tasks such as partitioning. You
-cannot clear the cache when Traffic Server is running.
-
-To clear the cache:
-
-#. Stop Traffic Server (see :ref:`stop-traffic-server`)
-#. Enter the following command to clear the cache::
-
-        traffic_server -Cclear
-
-   The ``clear`` command deletes all data in the object store and the
-   host database. Traffic Server does not prompt you to confirm the
-   deletion.
-
-#. Restart Traffic Server (see :ref:`start-traffic-server`).
-
-Removing an Object From the Cache
-=================================
-
-Traffic Server accepts the custom HTTP request method ``PURGE`` when
-removing a specific object from cache. If the object is found in the
-cache and is successfully removed, then Traffic Server responds with a
-``200 OK`` HTTP message; otherwise, a ``404 File Not Found`` message is
-returned.
-
-.. note::
-
-    By default, the PURGE request method is only processed if received on
-    the localhost interface.
-
-In the following example, Traffic Server is running on the domain
-``example.com`` and you want to remove the image ``remove_me.jpg``
-from cache. Because by default we do not permit ``PURGE`` requests from
-any other IP, we connect to the daemon via localhost: ::
-
-      $ curl -X PURGE -H 'Host: example.com' -v "http://localhost/remove_me.jpg"
-      * About to connect() to localhost port 80 (#0)
-      * Trying 127.0.0.1... connected
-      * Connected to localhost (127.0.0.1) port 80 (#0)
-
-      > PURGE /remove_me.jpg HTTP/1.1
-      > User-Agent: curl/7.19.7
-      > Host: example.com
-      > Accept: */*
-      >
-      < HTTP/1.1 200 Ok
-      < Date: Thu, 08 Jan 2010 20:32:07 GMT
-      < Connection: keep-alive
-
-The next time Traffic Server receives a request for the removed object,
-it will contact the origin server to retrieve a new copy, which will replace
-the previously cached version in Traffic Server.
-
-This procedure only removes an object from a specific Traffic Server cache.
-Users may still see the old (removed) content if it was cached by intermediary
-caches or by the end-users' web browser.
-
-.. _inspecting-the-cache:
-
-Inspecting the Cache
-====================
-
-Traffic Server provides a Cache Inspector utility that enables you to
-view, delete, and invalidate URLs in the cache (HTTP only). The Cache
-Inspector utility is a powerful tool that's capable of deleting all
-the objects in your cache. Therefore, make sure that only authorized
-administrators are allowed to access this utility through proper use
-of the ``@src_ip`` option in :file:`remap.config` and the instructions
-detailed in :ref:`controlling-client-access-to-cache`.
-
-Accessing the Cache Inspector Utility
--------------------------------------
-
-To access the Cache Inspector utility:
-
-#. Set :ts:cv:`proxy.config.http_ui_enabled` to ``1``.
-#. To access the cache inspector in reverse proxy mode, you must add a
-   remap rule to :file:`remap.config` to expose the URL. This should be
-   restricted to a limited set of hosts using the ``@src_ip`` option.
-   To restrict access to the network 172.28.56.0/24, use ::
-
-      map http://yourhost.com/myCI/ http://{cache} @action=allow @src_ip=172.28.56.1-172.28.56.254
-
-#. Reload the Traffic Server configuration by running :option:`traffic_ctl config reload`.
-#. Open your web browser and go to the the following URL::
-
-      http://yourhost/myCI/
-
-   You will now be presented with the Cache Inspector interface.
-
-Using the Cache Inspector Utility
----------------------------------
-
-The Cache Inspector Utility provides several options that enable you to view and
-delete the contents of your cache.
-
-Lookup URL
-    Search for a particular URL in the cache. When Traffic Server finds the URL
-    in the cache, it will display details of the object that corresponds to the
-    URL (e.g. header length and number of alternates). The option to delete the
-    URL from the cache will be presented.
-
-Delete URL
-    Delete the object from the cache which corresponds to the given URL. Success
-    or failure will be indicated after a delete has been attempted.
-
-Regex Lookup
-    Search URLs within the cache using one or more regular expressions.
-
-Regex Delete
-    Deletes all objects from the cache which match the provided regular
-    expressions.
-
-Regex Invalidate
-    Marks any objects in the cache which match the given regular expressions as
-    stale. Traffic Server will contact the relevant origin server(s) to confirm
-    the validity and freshness of the cached object, updating the cached object
-    if necessary.
-
-.. note::
-
-    Only one administrator should delete and invalidate cache
-    entries from the Cache Inspector at any point in time. Changes made by
-    multiple administrators at the same time can lead to unpredictable
-    results.

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/admin/configuring-traffic-server.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/configuring-traffic-server.en.rst b/doc/admin/configuring-traffic-server.en.rst
deleted file mode 100644
index 60c50de..0000000
--- a/doc/admin/configuring-traffic-server.en.rst
+++ /dev/null
@@ -1,80 +0,0 @@
-.. _configuring-traffic-server:
-
-Configuring Traffic Server
-**************************
-
-.. 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.
-
-Traffic Server provides several options for configuring the system.
-
-.. toctree::
-   :maxdepth: 2
-
-.. _configure-using-traffic-line:
-
-Configure Traffic Server Using Traffic Line
-===========================================
-
-Traffic Line enables you to quickly and easily change your Traffic
-Server configuration via command-line interface.
-
-View Configuration Options in Traffic Line
-------------------------------------------
-
-To view a configuration setting, enter the following command::
-
-    traffic_ctl config get VARIABLE
-
-where *var* is the variable associated with the configuration
-option. For a list of variables, refer to :ref:`configuration-variables`.
-
-Change Configuration Options in Traffic Line
---------------------------------------------
-
-To change the value of a configuration setting, enter the following
-command::
-
-    traffic_config set VARIABLE VALUE
-
-where *var* is the variable associated with the configuration option
-and *value* is the value you want to use. For a list of the
-variables, see :ref:`configuration-variables`.
-
-Configure Traffic Server Using Configuration Files
-==================================================
-
-As an alternative to using Traffic Line, you can change
-Traffic Server configuration options by manually editing specific
-variables in :file:`records.config`.
-
-Traffic Server must reread the configuration files for any changes to take effect.
-This is done with :option:`traffic_ctl config reload`. Some configuration changes require a
-full restart of Traffic Server.
-
-The following is a sample portion of :file:`records.config`:
-
-.. figure:: ../static/images/admin/records.jpg
-   :align: center
-   :alt: Sample records.config file
-
-   Sample records.config file
-
-In addition to :file:`records.config`,
-Traffic Server provides other configuration files that are used to
-configure specific features. You can manually edit all configuration
-files as described in :ref:`configuration-file-reference`.

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/admin/event-logging-formats.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/event-logging-formats.en.rst b/doc/admin/event-logging-formats.en.rst
deleted file mode 100644
index 9302b2b..0000000
--- a/doc/admin/event-logging-formats.en.rst
+++ /dev/null
@@ -1,700 +0,0 @@
-.. _event-logging-formats:
-
-Event Logging Formats
-*********************
-
-.. 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.
-
-This document provides a reference for all the different logging formats
-Traffic Server supports.
-Rather than just reading about those formats, you may also want to try our
-`online event log builder <http://trafficserver.apache.org/logbuilder/>`_ for an interactive way of
-building and understanding log formats.
-
-.. toctree::
-   :maxdepth: 2
-
-.. _custom-logging-fields:
-
-Custom Logging Fields
-=====================
-
-The following list describes Traffic Server custom logging fields.
-
-.. _cqh:
-
-``{HTTP header field name}cqh``
-    Logs the information in the requested field of the client request
-    HTTP header. For example, ``%<{Accept-Language}cqh>`` logs the
-    ``Accept-Language:`` field in client request headers.
-
-    .. note::
-        ecqh is the urlencoded version of this map
-
-.. _pqh:
-
-``{HTTP header field name}pqh``
-    Logs the information in the requested field of the proxy request
-    HTTP header. For example, ``%<{Authorization}pqh>`` logs
-    the ``Authorization:`` field in proxy request headers.
-
-    .. note::
-        epqh is the urlencoded version of this map
-
-.. _psh:
-
-``{HTTP header field name}psh``
-    Logs the information in the requested field of the proxy response
-    HTTP header. For example, ``%<{Retry-After}psh>`` logs the
-    ``Retry-After:`` field in proxy response headers.
-
-    .. note::
-        epsh is the urlencoded version of this map
-
-.. _ssh:
-
-``{HTTP header field name}ssh``
-    Logs the information in the requested field of the server response
-    HTTP header. For example, ``%<{Age}ssh>`` logs the ``Age:`` field in
-    server response headers.
-
-    .. note::
-        essh is the urlencoded version of this map
-
-.. _cssh:
-
-``{HTTP header field name}cssh``
-    Logs the information in the requested field of the cached server response
-    HTTP header. For example, ``%<{Age}cssh>`` logs the ``Age:`` field in
-    the cached server response headers.
-
-    .. note::
-        ecssh is the urlencoded version of this map
-
-.. _caun:
-
-``caun``
-    The client authenticated username; result of the RFC931/ident lookup
-    of the client username.
-
-.. _cfsc:
-
-``cfsc``
-    The client finish status code; specifies whether the client request
-    to Traffic Server was successfully completed (``FIN``) or
-    interrupted (``INTR``).
-
-.. _chi:
-
-``chi``
-    The IP address of the client's host machine.
-
-.. _chih:
-
-``chih``
-    The IP address of the client's host machine in hexadecimal.
-
-.. _hii:
-
-``hii``
-    This is the incoming (interface) ip for traffic server, in otherwords this is the ip address the client connected to.
-
-.. _hiih:
-
-``hiih``
-    The the incoming (interface) ip in hexadecimal.
-
-.. _chp:
-
-``chp``
-    The port number of the client's host machine.
-
-.. _cqbl:
-
-``cqbl``
-    The client request transfer length; the body length in the client
-    request to Traffic Server (in bytes).
-
-.. _cqhl:
-
-``cqhl``
-    The client request header length; the header length in the client
-    request to Traffic Server.
-
-.. _cqhm:
-
-``cqhm``
-    The HTTP method in the client request to Traffic Server: ``GET``,
-    ``POST``, and so on (subset of ``cqtx``).
-
-.. _cqhv:
-
-``cqhv``
-    The client request HTTP version.
-
-.. _cqpv:
-
-``cqpv``
-    The client request protocol & version.
-
-.. _cqtd:
-
-``cqtd``
-    The client request timestamp. Specifies the date of the client
-    request in the format yyyy-mm-dd, where yyyy is the 4-digit year, mm
-    is the 2-digit month, and dd is the 2-digit day.
-
-.. _cqtn:
-
-``cqtn``
-    The client request timestamp; date and time of the client's request
-    (in the Netscape timestamp format).
-
-.. _cqtq:
-
-``cqtq``
-    The time of the client request since January 1, 1970 UTC (EPOCH), with millisecond resolution.
-
-.. _cqts:
-
-``cqts``
-    The time of the client request since January 1, 1970 UTC (EPOCH), with second resolution.
-
-.. _cqtt:
-
-``cqtt``
-    The client request timestamp. The time of the client request in the
-    format hh:mm:ss, where hh is the two-digit hour in 24-hour format,
-    mm is the two-digit minutes value, and ss is the 2-digit seconds
-    value (for example, 16:01:19).
-
-.. _cqtr:
-
-``cqtr``
-    The TCP reused status; indicates if this client request went through
-    an already established connection.
-
-.. _cqssl:
-
-``cqssl``
-    The SSL client request status indicates if this client connection
-    is over SSL.
-
-.. _cqssr:
-
-``cqssr``
-    The SSL session/ticket reused status; indicates if this request hit
-    the SSL session/ticket and avoided a full SSL handshake.
-
-.. _cqssv:
-
-``cqssv``
-    The SSL/TLS version used to communicate with the client.
-
-.. _cqssc:
-
-``cqssc``
-    The cipher used by ATS to communicate with the client over SSL.
-
-.. _cqtx:
-
-``cqtx``
-    The full HTTP client request text, minus headers; for example, ::
-
-         GET http://www.company.com HTTP/1.0
-
-    In reverse proxy mode, Traffic Server logs the rewritten/mapped URL
-    (according to the rules in :file:`remap.config`), _not_ the
-    pristine/unmapped URL.
-
-.. _cqu:
-
-``cqu``
-    The universal resource identifier (URI) of the request from client
-    to Traffic Server (subset of ``cqtx`` ).
-
-    In reverse proxy mode, Traffic Server logs the rewritten/mapped URL
-    (according to the rules in :file:`remap.config`), _not_ the
-    pristine/unmapped URL.
-
-.. _cquc:
-
-``cquc``
-    The client request canonical URL. This differs from ``cqu`` in that
-    blanks (and other characters that might not be parsed by log
-    analysis tools) are replaced by escape sequences. The escape
-    sequence is a percentage sign followed by the ASCII code number in
-    hex.
-
-    See `cquuc`_.
-
-.. _cqup:
-
-``cqup``
-    The client request URL path; specifies the argument portion of the
-    URL (everything after the host). For example, if the URL is
-    ``http://www.company.com/images/x.gif``, then this field displays
-    ``/images/x.gif``
-
-    See `cquup`_.
-
-.. _cqus:
-
-``cqus``
-    The client request URL scheme.
-
-.. _cquuc:
-
-``cquuc``
-    The client request unmapped URL canonical. This field records a URL
-    before it is remapped (reverse proxy mode).
-
-.. _cquup:
-
-``cquup``
-    The client request unmapped URL path. This field records a URL path
-    before it is remapped (reverse proxy mode).
-
-.. _cquuh:
-
-``cquuh``
-    The client request unmapped URL host. This field records a URL's
-    host before it is remapped (reverse proxy mode).
-
-.. _cluc:
-
-``cluc``
-    The cache lookup URL, or cache key, for the client request. This URL is
-    canonicalized as well.
-
-.. _crat:
-
-``crat``
-    The Retry-After time in seconds, if specified by the origin server.
-
-.. _crc:
-
-``crc``
-    The cache result code; specifies how the cache responded to the
-    request (``HIT``, ``MISS``, and so on).
-
-.. _chm:
-
-``chm``
-    The cache hit-miss status, specifying which level of the cache this
-    was served out of. This is useful for example to show whether it was a
-    RAM cache vs disk cache hit. Future versions of the cache will support
-    more levels, but right now it only supports RAM (``HIT_RAM``) vs
-    rotational disk (``HIT_DISK``).
-
-.. _csscl:
-
-``csscl``
-    The cached response length (in bytes) from origin server to Traffic
-    Server.
-
-.. _csshl:
-
-``csshl``
-    The cached header length in the origin server response to Traffic
-    Server (in bytes).
-
-.. _csshv:
-
-``csshv``
-    The cached server response HTTP version (1.0, 1.1, etc.).
-
-.. _csssc:
-
-``csssc``
-    The cached HTTP response status code from origin server to Traffic
-    Server.
-
-.. _cwr:
-
-``cwr``
-    The cache write result (``-``, ``WL_MISS``, ``INTR```, ``ERR`` or ``FIN``)
-
-.. _cwtr:
-
-``cwtr``
-    The cache write transform result
-
-.. _fsiz:
-
-``fsiz``
-    The size of the file (*n* bytes) as seen by the origin server.
-
-
-.. _ms:
-
-``{Milestone field name}ms``
-    The timestamp in milliseconds of a specific milestone for this request.
-    see :c:func:`TSHttpTxnMilestoneGet` for milestone names.
-
-.. _msdms
-
-``{Milestone field name1-Milestone field name2}msdms``
-    The difference in milliseconds of between two milestones.
-    see :c:func:`TSHttpTxnMilestoneGet` for milestone names.
-
-
-.. _pfsc:
-
-``pfsc``
-    The proxy finish status code; specifies whether the Traffic Server
-    request to the origin server was successfully completed (``FIN``),
-    interrupted (``INTR``) or timed out (``TIMEOUT``).
-
-.. _phn:
-
-``phn``
-    The hostname of the Traffic Server that generated the log entry in
-    collated log files.
-
-.. _phi:
-
-``phi``
-    The IP of the Traffic Server that generated the log entry in
-    collated log files.
-
-.. _phr:
-
-``phr``
-    The proxy hierarchy route; the route Traffic Server used to retrieve
-    the object.
-
-.. _php:
-
-``php``
-    The TCP port number that Traffic Server served this request from.
-
-.. _piid:
-
-``piid``
-   The plugin ID for the transaction. This is set for plugin driven transactions via :c:func:`TSHttpConnectWithPluginId`.
-
-.. _pitag:
-
-``pitag``
-   The plugin tag for the transaction. This is set for plugin driven transactions via :c:func:`TSHttpConnectWithPluginId`.
-
-.. _pqbl:
-
-``pqbl``
-    The proxy request transfer length; the body length in Traffic
-    Server's request to the origin server.
-
-.. _pqhl:
-
-``pqhl``
-    The proxy request header length; the header length in Traffic
-    Server's request to the origin server.
-
-.. _pqsi:
-
-``pqsi``
-    The proxy request server IP address (0 on cache hits and parent-ip
-    for requests to parent proxies).
-
-.. _pqsn:
-
-``pqsn``
-    The proxy request server name; the name of the server that fulfilled
-    the request.
-
-.. _pscl:
-
-``pscl``
-    The length of the Traffic Server response to the client (in bytes).
-
-.. _psct:
-
-``psct``
-    The content type of the document from server response header: (for
-    example, ``img/gif`` ).
-
-.. _pshl:
-
-``pshl``
-    The header length in Traffic Server's response to the client.
-
-.. _psql:
-
-``psql``
-    The proxy response transfer length in Squid format (includes header
-    and content length).
-
-.. _pssc:
-
-``pssc``
-    The HTTP response status code from Traffic Server to the client.
-
-.. _pqssl:
-
-``pqssl``
-    Indicates whether the connection from Traffic Server to the origin
-    was over SSL or not.
-
-.. _shi:
-
-``shi``
-    The IP address resolved from the DNS name lookup of the host in the
-    request. For hosts with multiple IP addresses, this field records
-    the IP address resolved from that particular DNS lookup.
-
-    This can be misleading for cached documents. For example: if the
-    first request was a cache miss and came from *IP1* for server
-    *S* and the second request for server *S* resolved to
-    *IP2* but came from the cache, then the log entry for the
-    second request will show *IP2*.
-
-.. _shn:
-
-``shn``
-    The hostname of the origin server.
-
-.. _sscl:
-
-``sscl``
-    The response length (in bytes) from origin server to Traffic Server.
-
-.. _sshl:
-
-``sshl``
-    The header length (in bytes) in the origin server response to Traffic Server.
-
-.. _sshv:
-
-``sshv``
-    The server response HTTP version (1.0, 1.1, etc.).
-
-.. _sssc:
-
-``sssc``
-    The HTTP response status code from origin server to Traffic Server.
-
-.. _stms:
-
-``stms``
-    The time spent accessing the origin (in milliseconds); the time is
-    measured from the time the connection with the origin is established
-    to the time the connection is closed.
-
-.. _stmsh:
-
-``stmsh``
-    Same as ``stms`` but in hexadecimal.
-
-.. _stmsf:
-
-``stmsf``
-    The time Traffic Server spends accessing the origin as a fractional
-    number of seconds. That is, the time is formated as a floating-point
-    number, instead of an integer as in ``stms``.
-
-    For example: if the time is 1500 milliseconds, then this field
-    displays 1.5 while the ``stms`` field displays 1500 and the ``sts``
-    field displays 1.
-
-.. _sts:
-
-``sts``
-    The time Traffic Server spends accessing the origin, in seconds.
-
-.. _sstc:
-
-``sstc``
-    The number of transactions between Traffic Server and the origin server
-    from a single server session. A value greater than 0 indicates connection
-    reuse.
-
-.. _ttms:
-
-``ttms``
-    The time Traffic Server spends processing the client request; the
-    number of milliseconds between the time the client establishes the
-    connection with Traffic Server and the time Traffic Server sends the
-    last byte of the response back to the client.
-
-.. _ttmsh:
-
-``ttmsh``
-    Same as ``ttms`` but in hexadecimal.
-
-.. _ttmsf:
-
-``ttmsf``
-    The time Traffic Server spends processing the client request as a
-    fractional number of seconds. Time is specified in millisecond
-    resolution; however, instead of formatting the output as an integer
-    (as with ``ttms``), the display is formatted as a floating-point
-    number representing a fractional number of seconds.
-
-    For example: if the time is 1500 milliseconds, then this field
-    displays 1.5 while the ``ttms`` field displays 1500 and the ``tts``
-    field displays 1.
-
-.. _tts:
-
-``tts``
-    The time Traffic Server spends processing the client request; the
-    number of seconds between the time at which the client establishes
-    the connection with Traffic Server and the time at which Traffic
-    Server sends the last byte of the response back to the client.
-
-.. _logging-format-cross-reference:
-
-Logging Format Cross-Reference
-==============================
-
-The following sections illustrate the correspondence between Traffic
-Server logging fields and standard logging fields for the Squid and
-Netscape formats.
-
-Squid Logging Formats
----------------------
-
-The following is a list of the Squid logging fields and the
-corresponding logging field symbols.
-
-============== =============
-Squid          Field Symbols
-============== =============
-time           `cqts`_
-elapsed        `ttms`_
-client         `chi`_
-action/code    `crc`_/`pssc`_
-size           `psql`_
-method         `cqhm`_
-url            `cquc`_
-ident          `caun`_
-hierarchy/from `phr`_/`pqsn`_
-content        `psct`_
-============== =============
-
-Netscape Common Logging Formats
--------------------------------
-
-The following is a list of the Netscape Common logging fields and the
-corresponding Traffic Server logging field symbols.
-
-=============== =============
-Netscape Common Field Symbols
-=============== =============
-host            `chi`_
-usr             `caun`_
-[time]          [`cqtn`_]
-"req"           "`cqtx`_"
-s1              `pssc`_
-c1              `pscl`_
-=============== =============
-
-Netscape Extended Logging Formats
----------------------------------
-
-The following table lists the Netscape Extended logging fields and the
-corresponding Traffic Server logging field symbols.
-
-================= =============
-Netscape Extended Field Symbols
-================= =============
-host              `chi`_
-usr               `caun`_
-[time]            [`cqtn`_]
-"req"             "`cqtx`_"
-s1                `pssc`_
-c1                `pscl`_
-s2                `sssc`_
-c2                `sscl`_
-b1                `cqbl`_
-b2                `pqbl`_
-h1                `cqhl`_
-h2                `pshl`_
-h3                `pqhl`_
-h4                `sshl`_
-xt                `tts`_
-================= =============
-
-Netscape Extended-2 Logging Formats
------------------------------------
-
-The following is a list of the Netscape Extended-2 logging fields and
-the corresponding Traffic Server logging field symbols.
-
-=================== =============
-Netscape Extended-2 Field Symbols
-=================== =============
-``host``            ``chi``
-``usr``             ``caun``
-``[time]``          ``[cqtn]``
-``"req"``           ``"cqtx"``
-``s1``              ``pssc``
-``c1``              ``pscl``
-``s2``              ``sssc``
-``c2``              ``sscl``
-``b1``              ``cqbl``
-``b2``              ``pqbl``
-``h1``              ``cqhl``
-``h2``              ``pshl``
-``h3``              ``pqhl``
-``h4``              ``sshl``
-``xt``              ``tts``
-``route``           ``phr``
-``pfs``             ``cfsc``
-``ss``              ``pfsc``
-``crc``             ``crc``
-=================== =============
-
-.. _log-field-slicing:
-
-Log Field Slicing
-=================
-
-It is sometimes desirable to slice a log field to limit the length of a given
-log field's output.
-
-Log Field slicing can be specified as below:
-
-``%<field[start:end]>``
-``%<{field}container[start:end]>``
-
-Omitting the slice notation defaults to the entire log field.
-
-Slice notation only applies to a log field that is of type string
-and can not be applied to ip/timestamp which are converted to
-string from integer.
-
-The below slice specifiers are allowed.
-
-``[start:end]``
-          Log field value from start through end-1
-``[start:]``
-          Log field value from start through the rest of the string
-``[:end]``
-          Log field value from the beginning through end-1
-``[:]``
-          Default - entire Log field
-
-Some examples below ::
-
-  '%<cqup>'       //the whole characters of <cqup>.
-  '%<cqup>[:]'    //the whole characters of <cqup>.
-  '%<cqup[0:30]>' //the first 30 characters of <cqup>.
-  '%<cqup[-10:]>' //the last 10 characters of <cqup>.
-  '%<cqup[:-5]>'  //everything except the last 5 characters of <cqup>.

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/admin/explicit-proxy-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/explicit-proxy-caching.en.rst b/doc/admin/explicit-proxy-caching.en.rst
deleted file mode 100644
index 3608536..0000000
--- a/doc/admin/explicit-proxy-caching.en.rst
+++ /dev/null
@@ -1,83 +0,0 @@
-.. _explicit-proxy-caching:
-
-Explicit Proxy Caching
-**********************
-
-.. 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
-
-If you want to use Traffic Server as an explicit proxy cache, you must
-configure client software (i.e., browsers) to send requests directly to
-Traffic Server.
-
-If you do not configure Traffic Server to use the transparency option
-(with which client requests are intercepted en route to origin servers
-by a switch/router and rerouted to the Traffic Server machine), then
-clients must configure their web browsers to send HTTP requests to the
-Traffic Server proxy cache by configuring their browsers to download
-proxy configuration instructions from a :ref:`PAC file <using-a-pack-file>`
-(Proxy Auto-Configuration file).
-
-Configuring Browsers Manually
-=============================
-
-To manually configure a browser to send HTTP requests to Traffic Server,
-clients must provide the following information:
-
--  The fully-qualified hostname or IP address of the Traffic Server node
--  The Traffic Server proxy server port (by default, 8080)
-
-In addition, clients can specify not to use Traffic Server for certain
-sites - in such cases, requests to the listed sites go directly to the
-origin server. The procedures for manual configuration vary among
-browser versions; refer to specific browser documentation for complete
-proxy configuration instructions. You do not need to set any special
-configuration options on Traffic Server if you want to accept requests
-from manually-configured browsers.
-
-.. _using-a-pack-file:
-
-Using a PAC File
-================
-
-A *PAC file* is a specialized JavaScript function definition that a
-browser calls to determine how requests are handled. Clients must
-specify (in their browser settings) the URL from which the PAC file is
-loaded. You can store a PAC file on Traffic Server (or on any server in
-your network) and then provide the URL for this file to your clients.
-
-Sample PAC File
----------------
-
-The following sample PAC file instructs browsers to connect directly to
-all hosts without a fully-qualified domain name and to all hosts in the
-local domain. All other requests go to the Traffic Server named
-``myproxy.company.com``.::
-
-    function FindProxyForURL(url, host)
-    {
-      if (isPlainHostName(host)) || (localHostOrDomainIs(host, ".company.com")) {
-        return "DIRECT";
-      }
-      else
-        return "PROXY myproxy.company.com:8080; DIRECT";
-    }
-
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/admin/faqs.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/faqs.en.rst b/doc/admin/faqs.en.rst
deleted file mode 100644
index 15d775a..0000000
--- a/doc/admin/faqs.en.rst
+++ /dev/null
@@ -1,612 +0,0 @@
-.. _faqs:
-
-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 :manpage:`dd(1)`) and mount it as loopback device.
-This is accomplished with :manpage:`losetup(8)` on Linux, :manpage:`lofiadm(1m)` on Solaris
-and Illumos, and :manpage:`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
-can continue to download the object from the origin server, using the :ref:`background fill feature <background_fill>`.
-It will continue downloading based on the :ts:cv:`proxy.config.http.background_fill_active_timeout` and :ts:cv:`proxy.config.http.background_fill_completed_threshold` settings.
-
-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.
-These objects run entirely client-side (the system which originated
-the request for the objects), and do not execute on the server.
-
-In Squid- and Netscape-format log files, what do the cache result codes mean?
------------------------------------------------------------------------------
-
-This is described in detail in the :ref:`log-formats-squid-format` documentation.
-
-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 :file:`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.
-
-Refer to :ts:cv:`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 :file:`remap.config`. All
-other requests that do not match a map rule are 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 :ts:cv:`proxy.config.url_remap.remap_required`
-to ``1`` in :file:`records.config`.
-
-How do I enable forward proxy mode
-----------------------------------
-
-Please refer to the :ref:`forward-proxy` documentation.
-
-How do I interpret the Via: header code?
-----------------------------------------
-
-The ``Via`` header string can be decoded with the `Via Decoder Ring <http://trafficserver.apache.org/tools/via>`_.
-
-The Via header is an optional HTTP header added by Traffic Server and other HTTP proxies. If a request goes through multiple proxies, each one appends its Via header content to the end of the existing Via header. Via header content is for general information and diagnostic use only and should not be used as a programmatic interface to Traffic Server.
-
-The form of the Via header is
-
-Via: <protocol> <proxyname> (<product/version> [<via-codes>])
-
-================= ==========================
-Value             Meaning
-================= ==========================
-<protocol>        the scheme and version of the HTTP request
-<proxyname>       the configured name of the proxy server
-<product/version> the Traffic Server product name and version
-<via-codes>       a string of alphabetic codes presenting status information about the proxy handling of the HTTP request
-================= ==========================
-
-For example:
-Via: HTTP/1.0 storm (Traffic-Server/4.0.0   [cMs f ])
-
-- [u lH o  f  pS eN]     cache hit
-- [u lM oS fF pS eN]     cache miss
-- [uN l oS f  pS eN]     no-cache origin server fetch
-
-The short status code shows the cache-lookup, server-info and cache-fill information as listed in the full status code description below. The long status code list provided in older, commercial versions of Traffic Server can be restored by setting the verbose_via_str config variable.
-The character strings in the via-code show [<request results>:<proxy op>] where <request results> represents status information about the results of the client request and <proxy op> represent some information about the proxy operations performed during request processing. The full via-code status format is
-
-[u<client-info> c<cache-lookup> s<server-info> f<cache-fill> p<proxy-info> e<error-codes> : t<tunnel-info>c<cache-type><cache-lookup-result> i<icp-conn-info> p<parent-proxy> s<server-conn-info>]
-
-
-u client-info
-^^^^^^^^^^^^^^^^^^^^^
-
-Request headers received from client. Value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-C     cookie
-E     error in request
-I     If Modified Since (IMS)
-N     no-cache
-S     simple request (not conditional)
-===== ==========================
-
-c cache-lookup
-^^^^^^^^^^^^^^^^^^^^^
-Result of Traffic Server cache lookup for URL. Value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-A     in cache, not acceptable (a cache "MISS")
-H     in cache, fresh (a cache "HIT")
-M     miss (a cache "MISS")
-R     in cache, fresh RAM hit (a cache "HIT")
-S     in cache, stale (a cache "MISS")
-blank no cache lookup performed
-===== ==========================
-
-s server-info
-^^^^^^^^^^^^^^^^^^^^^
-Response information received from origin server. Value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-E     error in response
-N     not-modified
-S     served
-blank no server connection needed
-===== ==========================
-
-f cache-fill
-^^^^^^^^^^^^^^^^^^^^^
-Result of document write to cache. Value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-D     cached copy deleted
-U     updated old cache copy
-W     written into cache (new copy)
-blank no cache write performed
-===== ==========================
-
-p proxy-info
-^^^^^^^^^^^^^^^^^^^^^
-Proxy operation result. Value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-N     not-modified
-R     origin server revalidated
-S     served
-===== ==========================
-
-e error-codes
-^^^^^^^^^^^^^^^^^^^^^
-
-Value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-A     authorization failure
-C     connection to server failed
-D     dns failure
-F     request forbidden
-H     header syntax unacceptable
-N     no error
-R     cache read error
-S     server related error
-T     connection timed out
-===== ==========================
-
-: = Separates proxy request result information from operation detail codes
-
-t tunnel-info
-^^^^^^^^^^^^^^^^^^^^^
-Proxy-only service operation. Value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-A     tunnel authorization
-F     tunneling due to a header field (such as presence of If-Range header)
-M     tunneling due to a method (e.g. CONNECT)
-N     tunneling due to no forward
-O     tunneling because cache is turned off
-U     tunneling because of url (url suggests dynamic content)
-blank no tunneling
-===== ==========================
-
-c cache-type and cache-lookup
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-cache result values (2 characters)
-
-cache-type character value is one of
-
-===== ==========================
-Value             Meaning
-===== ==========================
-C     cache
-I     icp
-L     cluster, (not used)
-P     parent
-S     server
-blank cache miss or no cache lookup
-===== ==========================
-
-cache-lookup-result character value is one of:
-
-===== ==========================
-Value             Meaning
-===== ==========================
-C     cache hit, but config forces revalidate
-D     cache hit, but method forces revalidated (e.g. ftp, not anonymous)
-H     cache hit
-I     conditional miss (client sent conditional, fresh in cache, returned 412)
-K     cookie miss
-M     cache miss (url not in cache)
-N     conditional hit (client sent conditional, doc fresh in cache, returned 304)
-S     cache hit, but expired
-U     cache hit, but client forces revalidate (e.g. Pragma: no-cache)
-blank no cache lookup
-===== ==========================
-
-i icp-conn-info
-^^^^^^^^^^^^^^^^^^^^^
-
-ICP status
-
-===== ==========================
-Value             Meaning
-===== ==========================
-F     connection open failed
-S     connection opened successfully
-blank no icp
-===== ==========================
-
-p parent-proxy
-^^^^^^^^^^^^^^^^^^^^^
-parent proxy connection status
-
-===== ==========================
-Value             Meaning
-===== ==========================
-F     connection open failed
-S     connection opened successfully
-blank no parent proxy
-===== ==========================
-
-s server-conn-info
-^^^^^^^^^^^^^^^^^^^^^
-origin server connection status
-
-===== ==========================
-Value             Meaning
-===== ==========================
-F     connection open failed
-S     connection opened successfully
-blank no server connection
-===== ==========================
-
-
-
-Support for HTTP Expect: Header
--------------------------------
-
-Traffic Server currently does not handle Expect: request headers
-according to the HTTP/1.1 spec.
-
-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::
-
-   curl -H"Expect:" http://www.example.com/
-
-Or with the C (libcurl) library from within your own applications::
-
-   struct curl_slist *header_list=NULL;
-   header_list = curl_slist_append(header_list, "Expect:");
-   curl_easy_setopt(my_curlp, CURLOPT_HTTPHEADER, header_list);
-
-Or with the PHP cURL library::
-
-   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 :program:`traffic_manager` process is running by entering the
-    following command::
-
-        pgrep -l traffic_manager
-
-    If the :program:`traffic_manager` process is not running, then enter the
-    following command from the Traffic Server ``bin`` directory to start it::
-
-        ./traffic_manager
-
-.. XXX: this is wrong
-
-    You should always start and stop Traffic Server with the
-    :program:`trafficserver start` and :program:`trafficserver stop` commands to ensure
-    that all the processes start and stop correctly. For more information,
-    refer to :ref:`getting-started`.
-
-**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_ctl -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 :manpage:`resolv.conf(5)` file contains valid IP addresses
-   for your DNS servers.
--  On some systems, if the :manpage:`resolv.conf(5)` 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 :manpage:`resolv.conf(5)` file.
--  Check that the Traffic Server user account has permission to read the
-   :manpage:`resolv.conf(5)` 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 :ts:cv:`proxy.config.cache.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
-these requests. This error does not cause any Traffic Server problems. The
-misconfigured browser must be reconfigured to use the correct proxy
-port. Traffic Server clusters should ideally be 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 "var/trafficserver/no_cop" file...exiting
-
-The file ``var/trafficserver/no_cop`` acts as an administrative control
-that instructs the :program:`traffic_cop` process to exit immediately without
-starting :program:`traffic_manager` or performing any health checks. The
-``no_cop`` file prevents Traffic Server from starting automatically when
-it has been stopped with the option:`trafficserver stop` 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: ::
-
-   trafficserver start
-
-Warning in the system log file when manually editing vaddrs.config
-------------------------------------------------------------------
-
-If you manually edit :file:`vaddrs.config` 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 as Traffic Server will still 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 that no log files
-exist.
-
-If Traffic Server is not idle, and you still do not see log files being
-generated, verify the following:
-
-- Make sure you're looking in the correct directory. By default, Traffic
-  Server creates log files in the ``logs`` directory. This can be modified
-  by changing :ts:cv:`proxy.config.log.logfile_dir` in :file:`records.config`.
-
-- 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 :program:`traffic_server` process will be unable to
-  open or create log files.
-
-- Check that logging is enabled by checking the value of the
-  :ts:cv:`proxy.config.log.logging_enabled` variable in :file:`records.config`.
-
-- Check that a log format is enabled. In :file:`records.config`, 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 either client or origin server connections reach 90% of half the
-configured total 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:
-
-Connection Spike
-    Too many client requests (enough to exceed your configured maximum connections)
-    all reach Traffic Server at the same time. Such events are typically transient
-    and require no corrective action if your connection limits are already
-    configured appropriately for your Traffic Server and origin resources.
-
-Service Overload
-    Client requests are arriving at a rate faster than that which Traffic
-    Server can service them. This may indicate network problems between Traffic
-    Server and origin servers or that Traffic Server may require more memory, CPU,
-    cache disks, or other resources to handle the client load.
-
-If necessary, you can adjust the maximum number of connections supported
-by Traffic Server by editing :ts:cv:`proxy.config.net.connections_throttle` in
-:file:`records.config`.
-
-.. note::
-
-    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.
-
-Config checker
---------------
-
-Traffic Server supports the below command to validate the config offline, inorder to
-allow the config to be pre-checked for possible service disruptions due to synatx errors::
-
-   traffic_server -Cverify_config -D<config_dir>
-
-<config_dir> is the location of the config files to be validated.
-
-Connection timeouts with the origin server
-------------------------------------------
-
-By default, Traffic Server will timeout after 30 seconds when contacting
-origin servers. If you cannot avoid such timeouts by otherwise addressing the
-performance on your origin servers, you may adjust the origin connection timeout
-in Traffic Server by changing :ts:cv:`proxy.config.http.connect_attempts_timeout`
-in :file:`records.config` to a larger value.
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/admin/forward-proxy.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/forward-proxy.en.rst b/doc/admin/forward-proxy.en.rst
deleted file mode 100644
index cee8ba6..0000000
--- a/doc/admin/forward-proxy.en.rst
+++ /dev/null
@@ -1,118 +0,0 @@
-.. _forward-proxy:
-
-Forward Proxy
-*************
-
-.. 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 Apache Traffic Server is a general purpose proxy, configurable as both a
-reverse and forward proxy.
-
-A forward proxy can be used as a central tool in your infrastructure
-to access the web and it may be combined with a cache to lower your overall
-bandwidth usage. Forward proxies act as a gatekeeper between client browsers
-on your local network and all (or some, at your configuration's discretion)
-web sites accessed by those clients. The forward proxy will receive the
-HTTP requests, perform any filtering or request alteration rules you
-establish, and when appropriate forward the request on to its destination
-website. The response will return through your proxy, where it may optionally
-be cached and/or modified, and then returned to the original client.
-
-There are two modes in which your forward proxy may operate:
-
-Forward Proxy
-    Each client must be configured explicitly to use the forward proxy. Client
-    browsers will be aware of the fact they are using a proxy and will form their
-    HTTP requests appropriately. This results in the initial HTTP command being
-    issued with fully qualified URIs that contain the destination hostname::
-
-        GET http://example.com/index.php?id=123 HTTP/1.1
-
-Transparent Proxy
-    The use of a transparent proxy is typically done in concert with network
-    routing rules which redirect all outbound HTTP traffic through your proxy.
-    Clients will behave, and form their HTTP requests, as if they are contacting
-    the remote site directly, and will not be aware of the existence of a proxy
-    server in between themselves and the remote servers. HTTP requests will be
-    generated per their usual form, with only paths in the command and a
-    separate Host request header::
-
-        GET /index?id=123 HTTP/1.1
-        Host: example.com
-
-Apache Traffic Server may be configured to operate as both a forward and
-a transparent proxy simultaneously.
-
-Proxy Configuration
-===================
-
-Configuring basic forward proxy operation in Traffic Server is quite simple
-and straightforward.
-
-1. Permit Traffic Server to process requests for hosts not explicitly configured
-   in the remap rules, by modifying :ts:cv:`proxy.config.url_remap.remap_required`
-   in :file:`records.config`::
-
-        CONFIG proxy.config.url_remap.remap_required INT 0
-
-2. *Optional*: If Traffic Server will be operating strictly as a forward proxy,
-   you will want to disable reverse proxy support by modifying
-   :ts:cv:`proxy.config.reverse_proxy.enabled` in :file:`records.config`::
-
-        CONFIG proxy.config.reverse_proxy.enabled INT 0
-
-You may also want to consider some of these configuration options:
-
-- Setting :ts:cv:`proxy.config.http.no_dns_just_forward_to_parent` determines which
-  host will be used for DNS resolution.
-
-- Proxy Authentication can be enabled or disabled with
-  :ts:cv:`proxy.config.http.forward.proxy_auth_to_parent` should you also be
-  employing a proxy cache.
-
-- The client request header X-Forwarded-For may be toggled with
-  :ts:cv:`proxy.config.http.insert_squid_x_forwarded_for`.
-
-Client Configuration
-====================
-
-If you are operating your proxy in transparent mode, your clients should require
-no special proxy-related configuration.
-
-If you are operating in explicit forward proxy mode, without automatic routing
-rules on your network to direct all outbound traffic through the proxy, your
-client browsers will need to be directed to the proxy. This may be accomplished
-in two different ways.
-
-Clients may be configured to use the default ``8080`` port on your Traffic Server
-host as a proxy. This will result in all requests from that client browser being
-issued through the single forward proxy as configured.
-
-Security Considerations
-=======================
-
-It's important to note that once your Apache Traffic Server is configured as a
-forward proxy it will indiscriminately accept proxy requests from anyone. If it
-is reachable from the Internet, then you have configured an *Open Proxy*.
-
-This is generally not desirable, as it will permit anyone to potentially use
-your network as the source of traffic to sites of their choosing. To avoid
-this, you'll have to make sure your proxy server is either only reachable from
-within your private network or is secured by firewall rules that permit only
-those you wish to have access to the proxy.
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/admin/getting-started.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/getting-started.en.rst b/doc/admin/getting-started.en.rst
deleted file mode 100644
index 16c6f47..0000000
--- a/doc/admin/getting-started.en.rst
+++ /dev/null
@@ -1,209 +0,0 @@
-.. _admin-getting-started:
-
-Admin - Getting Started
-***********************
-
-.. 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
-
-Before You Start
-================
-
-Before you get started with Traffic Server you may have to decide which
-version you want to use. Traffic Server follows the `Semantic Versioning
-<http://semver.org>`_ guidelines.
-
-A complete version number is made of a version-triplet: ``MAJOR.MINOR.PATCH``.
-
-As of v4.0.0, there are no longer any development (or unstable) releases.
-All releases are considered stable and ready for production use. Releases
-within a major version are always upgrade compatible. More details are
-available on the `New Release Processes
-<https://cwiki.apache.org/confluence/display/TS/Release+Process>`_ wiki
-page.
-
-Sometimes we speak of *trunk*, *master* or *HEAD*, all of which are used
-interchangeably. Trunk and master, or sometimes TIP or HEAD, refer to the
-latest code in a Git version control system (also referred to as a *repository*
-or *Git repo*). Master is always kept releasable, and compatible with the
-current major release version. Incompatible changes are sometimes committed on
-a next-major release branch; for example, we have the ``5.0.x`` branch where
-changes incompatible with 4.x are managed.
-
-If your distribution does not come with a prepackaged Traffic Server,
-please go to `downloads <https://trafficserver.apache.org/downloads>`_ to choose the version that you
-consider most appropriate for yourself. If you want to really be on the
-bleeding edge you can clone our `git
-repository <https://git-wip-us.apache.org/repos/asf/trafficserver.git>`_.
-
-.. note::
-
-    We do also have a `GitHub Mirror <https://github.com/apache/trafficserver>`_
-    that you may use to submit pull requests. However, it may not be
-    entirely up-to-date, and you should always refer to our official project
-    Git repository for the very latest state of the source code.
-
-Building Traffic Server
-=======================
-
-In order to build Traffic Server from source you will need the following
-development tools and libraries installed:
-
--  pkgconfig
--  libtool
--  gcc (>= 4.3 or clang > 3.0)
--  GNU make
--  openssl
--  tcl
--  expat
--  pcre
--  libcap
--  flex (for TPROXY)
--  hwloc
--  lua
--  curses (for :program:`traffic_top`)
--  curl (for :program:`traffic_top`)
-
-If you're building from a git clone, you'll also need:
-
--  git
--  autoconf
--  automake
-
-The following instructions demonstrate building a fresh Traffic Server from
-Git sources.
-
-#. Clone the official Git repository for Traffic Server. ::
-
-    git clone https://git-wip-us.apache.org/repos/asf/trafficserver.git
-
-#. Change your work directory to the newly-cloned local repository and run autoreconf. ::
-
-    cd trafficserver/
-    autoreconf -if
-
-#. A ``configure`` script will be generated from ``configure.ac`` which may now
-   be used to configure the source tree for your build. ::
-
-    ./configure --prefix=/opt/ats
-
-   By default, Traffic Server will be built to use the ``nobody`` user and group.
-   You may change this with the ``--with-user`` argument to ``configure``::
-
-    ./configure --prefix=/opt/ats --with-user=tserver
-
-   If dependencies are not in standard paths (``/usr/local`` or ``/usr``),
-   you may need to pass options to ``configure`` to account for that::
-
-    ./configure --prefix=/opt/ats --with-lua=/opt/csw
-
-   Most ``configure`` path-options accept a format of "*INCLUDE_PATH*:*LIBRARY_PATH*"::
-
-    ./configure --prefix=/opt/ats --with-pcre=/opt/csw/include:/opt/csw/lib/amd64
-
-#. Once the source tree has been configured, you may proceed on to building with
-   the generated Makefiles. The ``make check`` command may be used to perform
-   sanity checks on the resulting build, prior to installation, and it is
-   recommended that you use this. ::
-
-    make
-    make check
-
-#. With the source built and checked, you may now install all of the binaries,
-   header files, documentation, and other artifacts to their final locations on
-   your system. ::
-
-    sudo make install
-
-#. Finally, it is recommended that you run the regression test suite. Please note
-   that the regression tests will only be successful with the default layout. ::
-
-    cd /opt/ats
-    sudo bin/traffic_server -R 1
-
-.. _build-traffic-server-with-spdy:
-
-Building Traffic Server with SPDY
-=================================
-
-Traffic Server v5.0.x and above support SPDY. The following instructions demonstrate
-building a fresh Traffic Server with SPDY enabled from Git sources.
-
-#. Clone the spdylay Git repository from tatsuhiro. ::
-
-    git clone https://github.com/tatsuhiro-t/spdylay
-
-#. The below steps will build spdylay library and set the PKG_CONFIG_PATH ::
-
-    cd spdylay/
-    autoreconf -if
-    ./configure --prefix=/opt/spdylay
-    make install
-    export PKG_CONFIG_PATH=/opt/spdylay/lib/pkgconfig/
-
-#. Finally, you can build trafficserver following the steps in the previous section along
-   with an additional option --enable-spdy as below  ::
-
-    ./configure --enable-spdy
-
-You are now ready to configure and run your Traffic Server installation.
-
-.. _start-traffic-server:
-
-Start Traffic Server
-====================
-
-To start Traffic Server manually, issue the ``trafficserver`` command,
-passing in the subcommand ``start``. This command starts all the
-processes that work together to process Traffic Server requests as well
-as manage, control, and monitor the health of the Traffic Server system. ::
-
-   bin/trafficserver start
-
-
-The :program:`traffic_ctl` provides a quick way of viewing Traffic Server statistics
-and configuring the Traffic Server system via a command-line interface.
-
-:program:`traffic_ctl` commands take the following form::
-
-     bin/traffic_ctl COMMAND COMMAND ...
-
-For a list of :program:`traffic_ctl` commands, enter::
-
-     bin/traffic_ctl
-
-Please note that :program:`traffic_ctl`, while a fine tool for an
-administrator, is a poor choice for automation, especially that of
-monitoring. See our chapter on :ref:`monitoring-traffic`
-for how to do that more efficiently and effectively.
-
-.. _stop-traffic-server:
-
-Stop Traffic Server
-===================
-
-To stop Traffic Server, always use the :program:`trafficserver` command,
-passing in the attribute ``stop``. This command stops all the Traffic
-Server processes (:program:`traffic_manager`, :program:`traffic_server`, and
-:program:`traffic_cop`). Do not manually stop processes, as this can lead to
-unpredictable results. ::
-
-    bin/trafficserver stop
-


Mime
View raw message