trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jpe...@apache.org
Subject [08/51] trafficserver git commit: Documentation reorganization
Date Tue, 03 Nov 2015 06:09:44 GMT
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/configuration/remap.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/configuration/remap.config.en.rst b/doc/reference/configuration/remap.config.en.rst
deleted file mode 100644
index 209d7ac..0000000
--- a/doc/reference/configuration/remap.config.en.rst
+++ /dev/null
@@ -1,495 +0,0 @@
-.. 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.
-
-============
-remap.config
-============
-
-.. configfile:: remap.config
-
-.. include:: ../../common.defs
-
-.. toctree::
-   :maxdepth: 2
-
-
-The :file:`remap.config` file (by default, located in
-``/usr/local/etc/trafficserver/``) 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  :ref:`reverse-proxy-and-http-redirects`, for information about
-redirecting HTTP requests and using reverse proxy.
-
-After you modify the :file:`remap.config` run the
-:option:`traffic_ctl config reload` 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 :file:`remap.config` file must contain a mapping rule. Empty lines,
-or lines starting with ``#`` are ignored. Each line can be broken up into multiple
-lines for better readability by using ``\`` as continuation marker.
-
-Traffic Server recognizes three space-delimited fields: ``type``,
-``target``, and ``replacement``. The following list describes the format of each field.
-
-.. _remap-config-format-type:
-
-``type``
-    Enter one of the following:
-
-    -  ``map`` --translates an incoming request URL to the appropriate
-       origin server URL.
-
-    -  ``map_with_recv_port`` --exactly like 'map' except that it uses the port at
-       which the request was received to perform the mapping instead of the port present
-       in the request. The regex qualifier can also be used for this type. When present,
-       'map_with_recv_port' mappings are checked first. If there is a match, then it is
-       chosen without evaluating the "regular" forward mapping rules.
-
-    -  ``map_with_referer`` -- extended version of 'map', which can be used to activate
-       "deep linking protection", where target URLs are only accessible when the Referer
-       header is set to a URL that is allowed to link to the target.
-
-    -  ``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).
-
-.. _remap-config-format-target:
-
-``target``
-    Enter the origin ("from") URL. You can enter up to four components: ::
-
-        scheme://host:port/path_prefix
-
-    where ``scheme`` is ``http``, ``https``, ``ws`` or ``wss``.
-
-.. _remap-config-format-replacement:
-
-``replacement``
-    Enter the origin ("from") URL. You can enter up to four components: ::
-
-        scheme://host:port/path_prefix
-
-    where ``scheme`` is ``http``, ``https``, ``ws`` or ``wss``.
-
-
-.. _remap-config-precedence:
-
-Precedence
-==========
-
-Remap rules are not processed top-down, but based on an internal
-priority. Once these rules are executed we pick the first match
-based on configuration file parse order.
-
-1. ``map_with_recv_port`` and ```regex_map_with_recv_port```
-#. ``map`` and ``regex_map`` and ``reverse_map``
-#. ``redirect`` and ``redirect_temporary``
-#. ``regex_redirect`` and ``regex_redirect_temporary``
-
-
-Match-All
-=========
-
-A map rule with a single ``/`` acts as a wildcard, it will match any
-request. This should be use with care, and certainly only once at the
-end of the remap.config file. E.g.
-
-::
-
-    map / http://all.example.com
-
-Examples
---------
-
-The following section shows example mapping rules in the
-:file:`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: ::
-
-    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: ::
-
-    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 :file:`remap.config`
-file.
-
-The following example shows a mapping with a path prefix specified in
-the target and replacement::
-
-    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::
-
-    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 Request
-================================ ======================================= =============================
-``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 :ts:cv:`proxy.config.header.parse.no_host_url_redirect`
-in the :file:`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/
-
-.. _remap-config-regex:
-
-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 (:ts:cv:`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
-
-.. _map_with_referer:
-
-map_with_referer
-================
-
-the format of is the following::
-
-    map_with_referer client-URL origin-server-URL redirect-URL regex1 [regex2 ...]
-
-'redirect-URL' is a redirection URL specified according to RFC 2616 and can
-contain special formatting instructions for run-time modifications of the
-resulting redirection URL.  All regexes Perl compatible  regular expressions,
-which describes the content of the "Referer" header which must be
-verified. In case an actual request does not have "Referer" header or it
-does not match with referer regular expression, the HTTP request will be
-redirected to 'redirect-URL'.
-
-At least one regular expressions must be specified in order to activate
-'deep linking protection'.  There are limitations for the number of referer
-regular expression strings - 2048.  In order to enable the 'deep linking
-protection' feature in Traffic Server, configure records.config with::
-
-    CONFIG proxy.config.http.referer_filter INT 1
-
-In order to enable run-time formatting for redirect URL, configure::
-
-    CONFIG proxy.config.http.referer_format_redirect INT 1
-
-When run-time formatting for redirect-URL was enabled the following format
-symbols can be used::
-
-    %r - to substitute original "Referer" header string
-    %f - to substitute client-URL from 'map_with_referer' record
-    %t - to substitute origin-server-URL from 'map_with_referer' record
-    %o - to substitute request URL to origin server, which was created a
-         the result of a mapping operation
-
-Note: There is a special referer type "~*" that can be used in order to
-specify that the Referer header is optional in the request.  If "~*" referer
-was used in map_with_referer mapping, only requests with Referer header will
-be verified for validity.  If the "~" symbol was specified before referer
-regular expression, it means that the request with a matching referer header
-will be redirected to redirectURL. It can be used to create a so-called
-negative referer list.  If "*" was used as a referer regular expression -
-all referers are allowed.  Various combinations of "*" and "~" in a referer
-list can be used to create different filtering rules.
-
-map_with_referer Examples
--------------------------
-
-::
-
-   map_with_referer http://y.foo.bar.com/x/yy/  http://foo.bar.com/x/yy/ http://games.bar.com/new_games .*\.bar\.com www.bar-friends.com
-
-Explanation: Referer header must be in the request, only ".*\.bar\.com" and "www.bar-friends.com" are allowed.
-
-::
-
-   map_with_referer http://y.foo.bar.com/x/yy/  http://foo.bar.com/x/yy/ http://games.bar.com/new_games * ~.*\.evil\.com
-
-Explanation: Referer header must be in the request but all referers are allowed except ".*\.evil\.com".
-
-::
-
-    map_with_referer http://y.foo.bar.com/x/yy/  http://foo.bar.com/x/yy/ http://games.bar.com/error ~* * ~.*\.evil\.com
-
-Explanation: Referer header is optional. However, if Referer header exists, only request from ".*\.evil\.com" will be redirected to redirect-URL.
-
-
-.. _remap-config-plugin-chaining:
-
-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
-
-.. _remap-config-named-filters:
-
-Acl Filters
-===========
-
-Acl filters can be created to control access of specific remap lines. The markup
-is very similar to that of :file:`ip_allow.config`, with slight changes to
-accomodate remap markup
-
-Examples
---------
-
-::
-
-    map http://foo.example.com/neverpost  http://foo.example.com/neverpost @action=deny @method=post
-    map http://foo.example.com/onlypost  http://foo.example.com/onlypost @action=allow @method=post
-
-    map http://foo.example.com/  http://foo.example.com/ @action=deny @src_ip=1.2.3.4
-    map http://foo.example.com/  http://foo.example.com/ @action=allow @src_ip=127.0.0.1
-    
-    map http://foo.example.com/  http://foo.example.com/ @action=allow @src_ip=10.5.2.1 @in_ip=72.209.23.4
-
-    map http://foo.example.com/  http://foo.example.com/ @action=allow @src_ip=127.0.0.1 @method=post @method=get @method=head
-
-Note that these Acl filters will return a 403 response if the resource is restricted.
-
-The difference between ``@src_ip`` and ``@in_ip`` is that the ``@src_ip`` is the client
-ip and the ``in_ip`` is the ip address the client is connecting to (the incoming address).
-
-Named Filters
-=============
-
-Named filters can be created and applied to blocks of mappings using
-the ``.definefilter``, ``.activatefilter``, and ``.deactivatefilter``
-directives. Named filters must be defined using ``.definefilter`` before
-being used. Once defined, ``.activatefilter`` can used to activate a
-filter for all mappings that follow until deactivated with
-``.deactivatefilter``.
-
-The ``@internal`` operator can be used to filter on whether a request
-is generated by |TS| itself, usually by a plugin.  This operator
-is helpful for remapping internal requests without allowing access
-to external users. By default both internal and external requests
-are allowed.
-
-
-Examples
---------
-
-::
-
-    .definefilter disable_delete_purge @action=deny @method=delete @method=purge
-    .definefilter local_only @action=allow @src_ip=192.168.0.1-192.168.0.254 @src_ip=10.0.0.1-10.0.0.254
-
-    .activatefilter disable_delete_purge
-
-    map http://foo.example.com/ http://bar.example.com/
-
-    .activatefilter local_only
-    map http://www.example.com/admin http://internal.example.com/admin
-    .deactivatefilter local_only
-
-    map http://www.example.com/ http://internal.example.com/
-    map http://auth.example.com/ http://auth.internal.example.com/ @action=allow @internal
-
-The filter `disable_delete_purge` will be applied to all of the
-mapping rules. (It is activated before any mappings and is never
-deactivated.) The filter `local_only` will only be applied to the
-second mapping.
-
-Including Additional Remap Files
-================================
-
-The ``.include`` directive allows mapping rules to be spread across
-multiple files. The argument to the ``.include`` directive is a
-list of file names to be parsed for additional mapping rules. Unless
-the names are absolute paths, they are resolved relative to the
-Traffic Server configuration directory.
-
-The effect of the ``.include`` directive is as if the contents of
-the listed files is included in the parent and parsing restarted
-at the point of inclusion. This means that and filters named in the
-included files are global in scope, and that additional ``.include``
-directives are allowed.
-
-.. note::
-
-  Included remap files are not currently tracked by the configuration
-  subsystem. Changes to included remap files will not be noticed
-  by online configuration changes applied by :option:`traffic_ctl config reload`
-  unless :file:`remap.config` has also changed.
-
-Examples
---------
-
-In this example, a top-level :file:`remap.config` file simply
-references additional mapping rules files ::
-
-  .include filters.config
-  .include one.example.com.config two.example.com.config
-
-The file `filters.config` contains ::
-
-  .definefilter deny_purge @action=deny @method=purge
-  .definefilter allow_purge @action=allow @method=purge
-
-The file `one.example.com.config` contains::
-
-  .activatefilter deny_purge
-  map http://one.example.com http://origin-one.example.com
-  .deactivatefilter deny_purge
-
-The file `two.example.com.config` contains::
-
-  .activatefilter allow_purge
-  map http://two.example.com http://origin-two.example.com
-  .deactivatefilter dallowpurge
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/configuration/splitdns.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/configuration/splitdns.config.en.rst b/doc/reference/configuration/splitdns.config.en.rst
deleted file mode 100644
index 8bc690b..0000000
--- a/doc/reference/configuration/splitdns.config.en.rst
+++ /dev/null
@@ -1,129 +0,0 @@
-.. 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.
-
-===============
-splitdns.config
-===============
-
-.. configfile:: splitdns.config
-
-The :file:`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 :ref:`configuring-dns-server-selection-split-dns`.
-
-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
-
-After you modify the :file:`splitdns.config` file,
-run the :option:`traffic_ctl config reload`
-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 :file:`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.
-
-.. _splitdns-config-format-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.
-
-.. _splitdns-config-format-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.
-
-.. _splitdns-config-format-url-regex:
-
-``url_regex``
-    A valid URL regular expression. This specifies that DNS server
-    selection will be based on a regular expression.
-
-.. _splitdns-config-format-named:
-
-``named``
-    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.
-
-.. _splitdns-config-format-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``
-
-.. _splitdns-config-format-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 :manpage:`resolv.conf(5)`
-
-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 :manpage:`resolv.conf(5)`
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/configuration/ssl_multicert.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/configuration/ssl_multicert.config.en.rst b/doc/reference/configuration/ssl_multicert.config.en.rst
deleted file mode 100644
index 0be58e6..0000000
--- a/doc/reference/configuration/ssl_multicert.config.en.rst
+++ /dev/null
@@ -1,228 +0,0 @@
-.. 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.
-
-====================
-ssl_multicert.config
-====================
-
-.. configfile:: ssl_multicert.config
-
-The :file:`ssl_multicert.config` file lets you configure Traffic
-Server to use multiple SSL server certificates to terminate the SSL
-sessions. 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 or host name.
-
-At configuration time, certificates are parsed to extract the
-certificate subject and all the DNS `subject alternative names
-<http://en.wikipedia.org/wiki/SubjectAltName>`_.  A certificate
-will be presented for connections requesting any of the hostnames
-found in the certificate. Wildcard names are supported, but only
-of the form `*.domain.com`, ie. where `*` is the leftmost domain
-component.
-
-Changes to :file:`ssl_multicert.config` can be applied to a running
-Traffic Server using :option:`traffic_ctl config reload`.
-
-Format
-======
-
-Each :file:`ssl_multicert.config` line consists of a sequence of
-`key=value` fields that specify how Traffic Server should use a
-particular SSL certificate.
-
-ssl_cert_name=FILENAME[,FILENAME ...]
-  The name of the file containing the TLS certificate. *FILENAME*
-  is located relative to the directory specified by the
-  :ts:cv:`proxy.config.ssl.server.cert.path` configuration variable.
-  It may also include the intermediate CA certificates, sorted from
-  leaf to root.  At a minimum, the file must include a leaf
-  certificate.
-
-  When running with OpenSSL 1.0.2 or later, this directive can be
-  used to configure the intermediate CA chain on a per-certificate
-  basis.  Multiple chain files are separated by comma character.
-  For example, it is possible able to configure a ECDSA certificate
-  chain and a RSA certificate chain and serve them simultaneously,
-  allowing OpenSSL to determine which certificate would be used
-  when the TLS session cipher suites are negotiated.  Note that the
-  leaf certs in `FILENAME1` and `FILENAME2` must have the same
-  subjects and alternate names. The first certificate is used to
-  to match the client's SNI request.
-
-  You can also configure multiple leaf certificates in a same chain
-  with OpenSSL 1.0.1.
-
-  This is the only field that is required to be present.
-
-dest_ip=ADDRESS (optional)
-  The IP (v4 or v6) address that the certificate should be presented
-  on. This is now only used as a fallback in the case that the TLS
-  SubjectNameIndication extension is not supported. If *ADDRESS* is
-  `*`, the corresponding certificate will be used as the global
-  default fallback if no other match can be made. The address may
-  contain a port specifier, in which case the corresponding certificate
-  will only match for connections accepted on the specified port.
-  IPv6 addresses must be enclosed by square brackets if they have
-  a port, eg, [::1]:80. Care should be taken to make each ADDRESS unique.
-
-ssl_key_name=FILENAME (optional)
-  The name of the file containing the private key for this certificate.
-  If the key is contained in the certificate file, this field can
-  be omitted, otherwise *FILENAME* is resolved relative to the
-  :ts:cv:`proxy.config.ssl.server.private_key.path` configuration variable.
-
-ssl_ca_name=FILENAME (optional)
-  If the certificate is issued by an authority that is not in the
-  system CA bundle, additional certificates may be needed to validate
-  the certificate chain. *FILENAME* is resolved relative to the
-  :ts:cv:`proxy.config.ssl.CA.cert.path` configuration variable.
-
-ssl_ticket_enabled=1|0 (optional)
-  Enable RFC 5077 stateless TLS session tickets. To support this,
-  OpenSSL should be upgraded to version 0.9.8f or higher. This
-  option must be set to `0` to disable session ticket support.
-
-ticket_key_name=FILENAME (optional)
-  The name of session ticket key file which contains a secret for
-  encrypting and decrypting TLS session tickets. If *FILENAME* is
-  not an absolute path, it is resolved relative to the
-  :ts:cv:`proxy.config.ssl.server.cert.path` configuration variable.
-  This option has no effect if session tickets are disabled by the
-  ``ssl_ticket_enabled`` option.  The contents of the key file should
-  be 48 random bytes.
-
-  Session ticket support is enabled by default. If neither of the
-  ``ssl_ticket_enabled`` and ``ticket_key_name`` options are
-  specified, and internal session ticket key is generated. This
-  key will be different each time Traffic Server is started.
-
-ssl_key_dialog=builtin|"exec:/path/to/program [args]" (optional)
-  Method used to provide a pass phrase for encrypted private keys.  If the
-  pass phrase is incorrect, SSL negotiation for this dest_ip will fail for
-  clients who attempt to connect.
-  Two options are supported: builtin and exec:
-
-    ``builtin`` - Requests pass phrase via stdin/stdout. User will be
-      provided the ssl_cert_name and be prompted for the pass phrase.
-      Useful for debugging.
-
-    ``exec:`` - Executes program /path/to/program and passes args, if
-      specified, to the program and reads the output from stdout for
-      the pass phrase.  If args are provided then the entire exec: string
-      must be quoted with "" (see examples).  Arguments with white space
-      are supported by single quoting (').  The intent is that this
-      program runs a security check to ensure that the system is not
-      compromised by an attacker before providing the pass phrase.
-
-Certificate Selection
-=====================
-
-Traffic Server attempts two certificate selections during SSL
-connection setup. An initial selection is made when a TCP connection
-is accepted. This selection examines the IP address and port that
-the client is connecting to and chooses the best certificate from
-the those that have a ``dest_ip`` specification. If no matching
-certificates are found, a default certificate is chosen.  The final
-certificate selection is made during the SSL handshake.  At this
-point, the client may use `Server Name Indication
-<http://en.wikipedia.org/wiki/Server_Name_Indication>`_ to request
-a specific hostname. Traffic Server will use this request to select
-a certificate with a matching subject or subject alternative name.
-Failing that, a wildcard certificate match is attempted. If no match
-can be made, the initial certificate selection remains in force.
-
-In all cases, Traffic Server attempts to select the most specific
-match. An address specification that contains a port number will
-take precedence over a specification that does not contain a port
-number. A specific certificate subject will take precedence over a
-wildcard certificate. In the case of multiple matching certificates
-the first match will be returned to non-SNI capable clients.
-
-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. Connections from all other IP addresses
-are terminated with the ``default.pem`` certificate.
-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
-    dest_ip=* ssl_cert_name=default.pem
-
-The following example configures Traffic Server to use the ECDSA
-certificate chain ``ecdsa.pem`` or RSA certificate chain ``rsa.pem``
-for all requests.
-
-::
-
-    dest_ip=* ssl_cert_name=ecdsa.pem,rsa.pem
-
-The following example configures Traffic Server to use the ECDSA
-certificate chain ``ecdsa.pem`` or RSA certificate chain ``rsa.pem``
-for all requests, the public key and private key are in separate PEM files.
-Note that the number of files in ssl_key_name must match the files in ssl_cert_name,
-and they should be presented in the same order.
-
-::
-
-    dest_ip=* ssl_cert_name=ecdsa_pub.pem,rsa_pub.pem ssl_key_name=ecdsa_private.pem,rsa_private.pem
-
-The following example configures Traffic Server to use the SSL
-certificate ``server.pem`` and the private key ``serverKey.pem``
-for all requests to port 8443 on IP address 111.11.11.1. The
-``general.pem`` certificate is used for server name matches.
-
-::
-
-     dest_ip=111.11.11.1:8443 ssl_cert_name=server.pem ssl_key_name=serverKey.pem ssl_cert_name=general.pem
-
-The following example configures Traffic Server to use the SSL
-certificate ``server.pem`` for all requests to the IP address
-111.11.11.1. Session tickets are enabled with a persistent ticket
-key.
-
-::
-
-    dest_ip=111.11.11.1 ssl_cert_name=server.pem ssl_ticket_enabled=1 ticket_key_name=ticket.key
-
-The following example configures Traffic Server to use the SSL
-certificate ``server.pem`` and disable session tickets for all
-requests to the IP address 111.11.11.1.
-
-::
-
-    dest_ip=111.11.11.1 ssl_cert_name=server.pem ssl_ticket_enabled=0
-
-The following examples configure Traffic Server to use the SSL
-certificate ``server.pem`` which includes an encrypted private key.
-The external program /usr/bin/mypass will be called on startup with one
-parameter (foo) in the first example, and with two parameters (foo)
-and (ba r) in the second example, the program (mypass) will return the
-pass phrase to decrypt the keys.
-
-::
-
-    ssl_cert_name=server1.pem ssl_key_dialog="exec:/usr/bin/mypass foo"
-    ssl_cert_name=server2.pem ssl_key_dialog="exec:/usr/bin/mypass foo 'ba r'"

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/configuration/storage.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/configuration/storage.config.en.rst b/doc/reference/configuration/storage.config.en.rst
deleted file mode 100644
index 1c958ba..0000000
--- a/doc/reference/configuration/storage.config.en.rst
+++ /dev/null
@@ -1,186 +0,0 @@
-.. 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.
-
-==============
-storage.config
-==============
-
-.. configfile:: storage.config
-
-The :file:`storage.config` file (by default, located in
-``/usr/local/etc/trafficserver/``) lists all the files, directories, and/or
-hard disk partitions that make up the Traffic Server cache. After you
-modify the :file:`storage.config` file the new settings will not be effective until Traffic Server is restarted.
-
-Format
-======
-
-The format of the :file:`storage.config` file is a series of lines of the form
-
-   *pathname* *size* [ ``volume=``\ *number* ] [ ``id=``\ *string* ]
-
-where :arg:`pathname` is the name of a partition, directory or file, :arg:`size` is the size of the
-named partition, directory or file (in bytes), and :arg:`volume` is the volume number used in the
-files :file:`volume.config` and :file:`hosting.config`. :arg:`id` is used for seeding the
-:ref:`assignment-table`. You must specify a size for directories; size is optional for files and raw
-partitions. :arg:`volume` and arg:`seed` are optional.
-
-.. note::
-
-   The :arg:`volume` option is independent of the :arg:`seed` option and either can be used with or without the other,
-   and their ordering on the line is irrelevant.
-
-.. note::
-
-   If the :arg:`id` option is used every use must have a unique value for :arg:`string`.
-
-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.
--  Group similar kinds of storage into different volumes. For example
-   split out SSD's or RAM drives into their own volume.
-
-Specify pathnames according to your operating system requirements. See
-the following examples. In the :file:`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 :ts:cv:`Traffic
-Server user <proxy.config.admin.user_id>` used by the Traffic Server process
-has read and write privileges on the raw disk device or partition. One good
-practice is to make sure the device file is set with 'g+rw' and the Traffic
-Server user is in the group which owns the device file.  However, some
-operating systems have stronger requirements - see the following examples for
-more information.
-
-As with standard ``records.config`` integers, human readable prefixes are also
-supported. They include
-
-   - ``K`` Kilobytes (1024 bytes)
-   - ``M`` Megabytes (1024^2 or 1,048,576 bytes)
-   - ``G`` Gigabytes (1024^3 or 1,073,741,824 bytes)
-   - ``T`` Terabytes (1024^4 or 1,099,511,627,776 bytes)
-
-.. _assignment-table:
-
-Assignment Table
-----------------
-
-Each storage element defined in :file:`storage.config` is divided in to :term:`stripes`. The
-assignment table maps from an object URL to a specific stripe. The table is initialized based on a
-pseudo-random process which is seeded by hashing a string for each stripe. This string is composed
-of a base string, an offset (the start of the stripe on the storage element), and the length of the
-stripe. By default the path for the storage is used as the base string. This ensures that each
-stripe has a unique string for the assignment hash. This does make the assignment table very
-sensitive to the path for the storage elements and changing even one can have a cascading effect
-which will effectively clear most of the cache. This can be problem when drives fail and a system
-reboot causes the path names to change.
-
-The :arg:`id` option can be used to create a fixed string that an administrator can use to keep the
-assignment table consistent by maintaing the mapping from physical device to base string even in the presence of hardware changes and failures.
-
-Examples
-========
-
-The following basic example shows 128 MB of cache storage in the
-``/big_dir`` directory::
-
-   /big_dir 134217728
-
-You can use the ``.`` symbol for the current directory. Here is an
-example for 64 MB of cache storage in the current directory::
-
-   . 134217728
-
-As an alternative, using the human readable prefixes, you can express a 64GB
-cache file with::
-
-   /really_big_dir 64G
-
-
-.. note::
-    When using on-filesystem cache disk storage, you can only have one such
-    directory specified. This will be address in a future version.
-
-
-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
--------------
-.. note::
-    Rather than refer to disk devices like ``/dev/sda``, ``/dev/sdb``, etc.,
-    modern Linux supports `alternative symlinked names for disk devices
-    <https://wiki.archlinux.org/index.php/persistent_block_device_naming#by-id_and_by-path>`_ in the ``/dev/disk``
-    directory structure. As noted for the :ref:`assignment-table` the path used for the disk can effect
-    the cache if it changes. This can be ameloriated in some cases by using one of the alternate paths
-    in via ``/dev/disk``. Note that if the ``by-id`` or ``by-path`` style is used, replacing a failed drive will cause
-    that path to change because the new drive will have a different physical ID or path. The original hash string can
-    be kept by adding :arg:`id` or :arg:`path` with the original path to the storage line.
-
-    If this is not sufficient then the :arg:`id` or :arg:`path` argument should be used to create a more permanent
-    assignment table. An example would be::
-
-       /dev/sde id=cache.disk.0
-       /dev/sdg id=cache.disk.1
-
-The following example will use an entire raw disk in the Linux operating
-system::
-
-   /dev/disk/by-id/[DiskA_ID]    volume=1
-   /dev/disk/by-path/[DiskB_Path]   volume=2
-
-In order to make sure :program:`traffic_server` will have access to this disk
-you can use :manpage:`udev(7)` 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 DiskA and DiskB to the tserver group
-   # make the assignment final, no later changes allowed to the group!
-   SUBSYSTEM=="block", KERNEL=="sd[ef]", GROUP:="tserver"
-
-In order to apply these settings, trigger a reload with :manpage:`udevadm(8)`:::
-
-   udevadm trigger --subsystem-match=block
-
-
-FreeBSD Example
----------------
-
-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::
-
-   /dev/ada1
-   /dev/ada2
-
-In order to make sure :program:`traffic_server` will have access to this disk
-you can use :manpage:`devfs(8)` to persistently set the right permissions. The
-following rules are stored in :manpage:`devfs.conf(5)`::
-
-   # 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/ce162a6d/doc/reference/configuration/volume.config.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/configuration/volume.config.en.rst b/doc/reference/configuration/volume.config.en.rst
deleted file mode 100644
index 7c6d594..0000000
--- a/doc/reference/configuration/volume.config.en.rst
+++ /dev/null
@@ -1,69 +0,0 @@
-.. 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.
-
-=============
-volume.config
-=============
-
-.. configfile:: volume.config
-
-The :file:`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
-:file:`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 :ref:`partitioning-the-cache`.
-
-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/ce162a6d/doc/reference/plugins/authproxy.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/authproxy.en.rst b/doc/reference/plugins/authproxy.en.rst
deleted file mode 100644
index d4a5e19..0000000
--- a/doc/reference/plugins/authproxy.en.rst
+++ /dev/null
@@ -1,110 +0,0 @@
-.. _authproxy-plugin:
-
-AuthProxy 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
-  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.
-
-There are many ways of authorizing an HTTP request. Often, this
-requires making IPC calls to some internal infrastructure. ``AuthProxy``
-is a plugin that takes care of the Traffic Server end of authorizing
-a request and delegates the authorization decision to an external
-HTTP service.
-
-This plugin can be used as either a global plugin or a remap plugin.
-
-Note that Traffic Server optimizes latency by skipping the DNS
-lookup state if a document is found in the cache. This will have
-the effect of serving the document without consulting the ``AuthProxy``
-plugin. you can disable this behavior by setting
-:ts:cv:`proxy.config.http.doc_in_cache_skip_dns` to ``0`` in
-:file:`records.config`.
-
-Note that the authorization request will need to match a remap rule 
-(which, as a standalone remap rule, does not need to call the 
-AuthProxy plugin). If a second remap rule is required, by default,
-the authorization request will not have the same Host header as 
-the request from the client. It could be added using the 
-``header_rewrite`` plugin (set-header Host "pristine_host.example.com").
-
-Plugin Options
---------------
-
---auth-transform=TYPE
-  This option specifies how to route the incoming request to the
-  authorization service. The transform type may be ``head`` or
-  ``redirect``.
-
-  If the transform type is ``head``, then the incoming request is
-  transformed to a HEAD request and is sent to the same destination.
-  If the response is ``200 OK``, the incoming request is allowed
-  to proceed.
-
-  If the transform type is ``range``, then the incoming request is
-  transformed to a Range request asking for 0 bytes. Other than that,
-  the behavior is identical to the ``head`` option above. This type
-  of Range request is useful when the upstream destination is a cache,
-  and it's not able to cache HEAD requests.
-
-  If the transform type is ``redirect`` then the incoming
-  request is sent to the authorization service designated by the
-  `--auth-host` and `--auth-port` parameters. If the response is
-  200 OK, the incoming request is allowed to proceed.
-
-  When the authorization service responds with a status other than
-  200 OK, that response is returned to the client as the response to
-  the incoming request. This allows mechanisms such as HTTP basic
-  authentication to work correctly. Note that the body of the
-  authorization service response is not returned to the client.
-
---auth-host=HOST
-  The name or address of the authorization host. This is only used
-  by the ``redirect`` transform.
-
---auth-port=PORT
-  The TCP port of the authorization host. This is only used by the
-  ``redirect`` transform.
-
---force-cacheability
-  If this options is set, the plugin will allow Traffic Server to
-  cache the result of authorized requests. In the normal case, requests
-  with authorization headers are nor cacheable, but this flag allows
-  that by setting the :ts:cv:`proxy.config.http.cache.ignore_authentication`
-  option on the request.
-
-Examples
---------
-
-In this example, the authentication is performed by converting the incoming
-HTTP request to a `HEAD` request and sending that to the origin server
-`origin.internal.com`::
-
-  map http://cache.example.com http://origin.internal.com/ \
-    @plugin=authproxy.so @pparam=--auth-transform=head
-
-  map http://origin.internal.com http://origin.internal.com/ 
-
-
-In this example, the request is directed to a local authentication server
-that authorizes the request based on internal policy rules::
-
-  map http://cache.example.com http://origin.internal.com/ \
-    @plugin=authproxy.so @pparam=--auth-transform=redirect @pparam=--auth-host=127.0.0.1 @pparam=--auth-port=9000
-
-  map http://origin.internal.com/ http://origin.internal.com/ \
-    @plugin=authproxy.so @pparam=--auth-transform=redirect @pparam=--auth-host=127.0.0.1 @pparam=--auth-port=9000    

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/background_fetch.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/background_fetch.en.rst b/doc/reference/plugins/background_fetch.en.rst
deleted file mode 100644
index 7826884..0000000
--- a/doc/reference/plugins/background_fetch.en.rst
+++ /dev/null
@@ -1,91 +0,0 @@
-.. _background-fetch-plugin:
-
-Background Fetch 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
-  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 is a plugin for Apache Traffic Server that allows you to proactively
-fetch content from Origin in a way that it will fill the object into
-cache. This is particularly useful when all (or most) of your client requests
-are of the byte-Range type. The underlying problem being that Traffic Server
-is not able to cache request / responses with byte ranges.
-
-Using the plugin
-----------------
-
-This plugin functions as either a global or per remap plugin, and it takes 
-an optional argument for specifying a config file with inclusion or 
-exclusion criteria. The config file can be specified both via an absolute
-path or via a relative path to the install dir
-
-To activate the plugin in global mode, in :file:`plugin.config`, simply add::
-
-  background_fetch.so --config <config-file>
-
-To activate the plugin in per remap mode, in :file:`remap.config`, simply append the
-below to the specific remap line::
-
-  @plugin=background_fetch.so @pparam=<config-file>
-
-Functionality
--------------
-
-Examining the responses from origin, we decide to trigger a background fetch
-of the original (Client) request under these conditions:
-
-- The request is a ``GET`` request (we only support these right now)
-- The response is a ``206`` response
-- The original client request, and the Origin server response, is clearly
-  indicating that the response is cacheable. This uses the new API
-  c:func:`TSHttpTxnIsCacheable()`, which also implies honoring current
-  Traffic Server configurations.
-
-
-Once deemed a good candidate to performance a background fetch, we'll replay
-the original client request through the Traffic Server proxy again, except
-this time eliminating the ``Range`` header. This is transparent to the
-original client request, which continues as normal.
-
-Only one background fetch per URL is ever performed, making sure we do not
-accidentally put pressure on the origin servers.
-
-The plugin now supports a config file that can specify exclusion or inclusion of 
-background fetch based on any arbitrary header or client-ip::
-
-  background_fetch.so --config <config-file>
-
-The contents of the config-file could be as below::
-
-  include User-Agent ABCDEF
-  exclude User-Agent *
-  exclude Content-Type text
-  exclude X-Foo-Bar text
-  exclude Content-Length <1000
-
-The plugin also now supports per remap activation. To activate the plugin for
-a given remap, add the below on the remap line::
-
-  @plugin=background_fetch.so @pparam=<config-file>
-
-Future additions
-----------------
-
-- Limiting the background fetches to content of certain sizes
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/balancer.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/balancer.en.rst b/doc/reference/plugins/balancer.en.rst
deleted file mode 100644
index b156028..0000000
--- a/doc/reference/plugins/balancer.en.rst
+++ /dev/null
@@ -1,83 +0,0 @@
-.. _balancer-plugin:
-
-Balancer 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
-  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 ``balancer`` balances requests across multiple origin servers.
-To use this plugin, configure it in a :file:`remap.config` rule, specifying
-a balancing policy and a set of origin servers. For example::
-
-   map http://foo.com http://foo.com \
-      @plugin=balancer.so @pparam=--policy=hash,url @pparam=one.bar.com @pparam=two.bar.com
-
-The ``replacement`` URL in the mapping rule is not used. The argument
-to the ``--policy`` option is a comma-separated list of keywords.
-The first keyword is the name of a balancing policy. The subsequent
-keywords are used to refine the requested policy.
-
-The remaining plugin arguments are balancer targets. Typically,
-these will be the host names of origin servers that requests should
-be balanced across. The target name may contain a colon-separated
-port number.
-
-Hash Balancing Policy
----------------------
-
-The ``hash`` balancing policy performs a consistent hash across the
-set of origins. This minimizes the number of hash entries that must
-be moved when the set of origin servers changes. An optional list
-of hash fields follows the ``hash`` keyword. Each specified hash
-field is hashed to select an outbound origin server.
-
-The following fields can be supplied to the hash:
-
-key
-  The request cache key. Note that the cache key will only be
-  set if you have already chained a plugin that sets a custom
-  cache key.
-
-url
-  The request URL. This is the default hash field that is used if
-  no other fields are specified.
-
-srcaddr
-  The source IP address of the request.
-
-dstaddr
-  The destination IP address of the request.
-
-Round Robin Balancing Policy
-----------------------------
-
-The ``roundrobin`` balancing policy simply allocates requests to
-origin servers in order. Over time, the number of requests received
-by each origin should be approximately the same.
-
-Health Checking
----------------
-
-The ``balancer`` plugin does not check the health of the origin
-servers, however the plugin is fully reloadable so health checking
-is usualy simple to implement. Most production environments already
-have mechanisms to check service health. It is recommended that you
-write a simple script to monitor this information and rewrite
-:file:`remap.config` when appropriate. Running :option:`traffic_ctl config reload`
-will reload the ``balancer`` plugin with the new set of origin servers.

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/buffer_upload.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/buffer_upload.en.rst b/doc/reference/plugins/buffer_upload.en.rst
deleted file mode 100644
index 7ae04bd..0000000
--- a/doc/reference/plugins/buffer_upload.en.rst
+++ /dev/null
@@ -1,82 +0,0 @@
-.. _buffer-upload-plugin:
-
-Buffer Upload 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
-  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 Buffer Upload plugin offers the following features
-
-Installation
-============
-
-Configuration can be explicitly specified as a parameter in ``plugin.config`` ::
-
-    buffer_upload.so /FOOBAR/upload.conf
-
-Memory buffering (buffer the entire POST data in IOBuffer before connecting to OS)
-==================================================================================
-
-Memory buffer size is configured with "mem_buffer_size" in config file. Default and minimum value is 32K. You can
-increase it in the config file. If the size of a request is larger than the "mem_buffer_size" value specifiied in the
-config file, then the upload proxy feature will be disabled for this particular request
-
-Disk buffering (buffer the entire POST data on disk before connecting to OS)
-============================================================================
-
-1. Disk async IO is used. AIO api call only involves certain amount of threads. The number of threads is configurable in
-plugin's config file (default is 4)
-
-2. Directories and files are generated on disk . Base directory is /FOOBAR/var/buffer_upload_tmp/ (configurable in
-config file). Number of subdirectories is 64 (configurable in config file). Filename are randomly generated. Files will
-be removed when the entire data have been sent out to OS . At startup time, dangling files are removed (left on disk due
-to transaction interruption or traffic server crash)
-
-3. Default chunk size when reading from disk is 16K, configurable in config file
-
-Trigger POST buffering on certain URLs
-======================================
-
-1. Certain URLs will be provided in a plain text file (one URL each line) 
-2. Specify filename in config file by "url_list_file" 
-3. max length of each URL is 4096 (configurable in config file) 
-4. use exact match, don't support regex for now
-
-Other Features 
-==============
-
-1. Default buffering mode is disk aio buffering mode. To turn off disk buffering, add a "use_disk_buffer 0" line in
-config file
-
-2. All request headers inlcuding cookies plus the entire POST data will be buffered (either in memory or on disk)
-
-Configuration File
-==================
-
-sample config file ::
-
-    use_disk_buffer 1 
-    convert_url 1 
-    chunk_size 1024 
-    url_list_file /tmp/url_list.conf 
-    max_url_length 10000 
-    base_dir /tmp/test1
-    subdir_num 100 
-    thread_num 10 
-    mem_buffer_size 40000
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/cacheurl.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/cacheurl.en.rst b/doc/reference/plugins/cacheurl.en.rst
deleted file mode 100644
index 1ad35bf..0000000
--- a/doc/reference/plugins/cacheurl.en.rst
+++ /dev/null
@@ -1,78 +0,0 @@
-.. _cacheurl-plugin:
-
-CacheURL 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
-  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 plugin allows you to change the key that is used for caching a
-request by using any portion of the url via regex. 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
-============
-
-This plugin is only built if the configure option ::
-
-    --enable-experimental-plugins
-
-is given at build time.
-
-Configuration
-=============
-
-Create a ``cacheurl.config`` file in the plugin directory with the url
-regex patterns to match. 
-
-``url_pattern   cache_key_replacement``
-
-
-The url_pattern is a regular expression (pcre). The replacement can contain $1, $2 and so on, which will be replaced with the appropriate matching group from the pattern.
-
-Add the plugin to your :file:`plugin.config` file::
-
-    cacheurl.so
-
-Start traffic server. Any rewritten URLs will be written to
-``cacheurl.log`` in the log directory by default.
-
-Examples
-========
-1. To make files from s1.example.com, s2.example.com and s3.example.com all be cached with the same key. Adding a unique suffix (TSINTERNAL in this example) to the cache key guarantees that it won't clash with a real URL should s.example.com exist.
-
-    ``http://s[123].example.com/(.*)  http://s.example.com.TSINTERNAL/$1``
-
-2. Cache based on only some parts of a query string (e.g. ignore session information). This plucks out the id and format query string variables and only considers those when making the cache key.
-
-    ``http://www.example.com/video\?.*?\&?(id=[0-9a-f]*).*?\&(format=[a-z]*) http://video-srv.example.com.ATSINTERNAL/$1&$2``
-
-3. Completely ignore a query string for a specific page
-
-    ``http://www.example.com/some/page.html(?:\?|$) http://www.example.com/some/page.html``
-
-More docs
-=============
-
-There are some docs on cacheurl in Chinese, please find them in the following:
-
-.. http://people.apache.org/~zym/trafficserver/cacheurl.html`` <http://people.apache.org/~zym/trafficserver/cacheurl.html>`_
-
-https://blog.zymlinux.net/index.php/archives/195

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/combo_handler.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/combo_handler.en.rst b/doc/reference/plugins/combo_handler.en.rst
deleted file mode 100644
index f851be6..0000000
--- a/doc/reference/plugins/combo_handler.en.rst
+++ /dev/null
@@ -1,85 +0,0 @@
-.. _combo-handler-plugin:
-
-Combohandler 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
-  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 plugin provides an intelligent way to combine multiple URLs into a single
-URL, and have Apache Traffic Server combine the components into one
-response. This is useful for example to create URLs that combine multiple CSS
-or Javascript files into one.
-
-Installation
-============
-
-This plugin is only built if the configure option ::
-
-    --enable-experimental-plugins
-
-is given at build time. Note that this plugin is built and installed in
-combination with the ESI module, since they share common code.
-
-Configuration
-=============
-
-The arguments in the :file:`plugin.config` line in order represent
-
-1. The path that should triggers combo handler (defaults to
-   "admin/v1/combo")
-
-2. The name of the key used for signature verification (disabled by
-   default)
-
-A "-" can be supplied as a value for any of these arguments to request
-default value be applied.
-
-Also, just like the original combohandler, this plugin generates URLs of
-the form ``http://localhost/<dir>/<file-path>``. ``<dir>`` here defaults
-to ``l`` unless specified by the file path in the query parameter using
-a colon. For example::
-
-    http://combo.com/admin/v1/combo?filepath1&dir1:filepath2&filepath3
-
-Will result in these three pages being fetched::
-
-    http://localhost/l/filepath1
-    http://localhost/dir1/filepath2
-    http://localhost/l/filepath3
-
-Remap rules have to be specified to map the above URLs to desired
-content servers.
-
-The plugin also supports a prefix parameter. Common parts of successive
-file paths can be extracted and specified separately using a 'p' query
-parameter. Successive file path parameters are appended to this prefix
-to create complete file paths. The prefix will remain active until
-changed or cleared (set to an empty string). For example, the query ::
-
-    "/file1&p=/path1/&file2&file3&p=&/file4&p=/dir:path2/&file5&file6"
-
-results in these file paths being "reconstructed"::
-
-    /file1
-    /path1/file2
-    /path1/file3
-    /file4
-    /dir:path2/file5
-    /dir:path2/file6
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/conf_remap.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/conf_remap.en.rst b/doc/reference/plugins/conf_remap.en.rst
deleted file mode 100644
index bcd974a..0000000
--- a/doc/reference/plugins/conf_remap.en.rst
+++ /dev/null
@@ -1,51 +0,0 @@
-.. 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.
-
-.. _conf-remap-plugin:
-
-conf_remap Plugin
-=================
-
-The `conf_remap` plugin allows you to override configuration
-directives dependent on actual remapping rules. The plugin is built
-and installed as part of the normal Apache Traffic Server installation
-process.
-
-The `conf_remap` plugin accepts configuration directives in the
-arguments list or in a separate configuration file. In both cases,
-only string and integer directives are supported.
-
-When using a separate configuration file, the standard
-:file:`records.config` syntax is used, for example::
-
-    map http://cdn.example.com/ http://some-server.example.com \
-      @plugin=conf_remap.so @pparam=/etc/trafficserver/cdn.conf
-
-where `cdn.conf` contains::
-
-    CONFIG proxy.config.url_remap.pristine_host_hdr INT 1
-
-When using inline arguments, the `conf_remap` plugin accepts a
-``key=value`` syntax, where the ``KEY`` is the name of the configuration
-directive and ``VALUE`` is the desired value, for example::
-
-    map http://cdn.example.com/ http://some-server.example.com \
-      @plugin=conf_remap.so @pparam=proxy.config.url_remap.pristine_host_hdr=1
-
-Doing this, you will override your global default configuration on
-a per mapping rule. For more details on the APIs, functionality, and a
-complete list of all overridable configurations, see :ref:`ts-overridable-config`.

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/epic.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/epic.en.rst b/doc/reference/plugins/epic.en.rst
deleted file mode 100644
index dcc74b3..0000000
--- a/doc/reference/plugins/epic.en.rst
+++ /dev/null
@@ -1,46 +0,0 @@
-.. _epic-plugin:
-
-Epic 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
-  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 `Epic` plugin emits Traffic Server metrics in a format that is
-consumed by the `Epic Network Monitoring System
-<https://code.google.com/p/epicnms/>`_.  It is a global plugin that
-is installed by adding it to the :file:`plugin.config` file.
-
-Plugin Options
---------------
-
---directory=DIR
-  Specify the directory the plugin will write sample files to. The
-  default is ``/usr/local/epic/cache/eapi``.
-
---period=SECS
-  Specify the sample period in seconds. The default is to write samples every
-  30 seconds.
-
-Caveats
--------
-
-The Traffic Server metrics system does not store the semantics of
-metrics, so it is not possible to programmatically determine whether
-a metrics can be rate converted. The plugin contains a static list
-of metrics that should not be rate converted (gauges in Epic
-terminilogy).

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/esi.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/esi.en.rst b/doc/reference/plugins/esi.en.rst
deleted file mode 100644
index 757cab7..0000000
--- a/doc/reference/plugins/esi.en.rst
+++ /dev/null
@@ -1,151 +0,0 @@
-.. _esi-plugin:
-
-ESI 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
-  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 plugin implements the ESI specification.
-
-Specification
-=============
-
-Supportted ESI tags:
-
-::
-
-    esi:include
-    esi:remove
-    esi:comment
-    esi:vars
-    esi:choose
-    esi:when
-    esi:otherwise
-    esi:try
-    esi:attempt
-    esi:except
-    <!--esi ... -->
-
-extended ESI tags: *esi:special-include*
-
-Supported variables:
-
-::
-
-    $(HTTP_HOST)
-    $(HTTP_REFERER)
-    $(HTTP_ACCEPT_LANGUAGE{name})
-    $(HTTP_COOKIE{name}) or $(HTTP_COOKIE{name;subkey})
-    $(QUERY_STRING{name})
-
-Note: the name is the key name such as "username", "id" etc. For cookie support sub-name or sub-key, the format is:
-name;subkey, such as "l;u", "l;t" etc. e.g. such cookie string: l=u=test&t=1350952328, the value of
-$(HTTP_COOKIE{"l;u"}) is test and the value of $(HTTP_COOKIE{"l;t"}) is 1350952328
-
-Compile and Installation
-========================
-
-This plugin is only built if the configure option ::
-
-    --enable-experimental-plugins
-
-is given at build time. Note that this plugin is built and installed in combination with the combo handler module, since
-they share common code.
-
-Enabling ESI
-============
-
-1. First we need to set up /usr/local/etc/trafficserver/plugin.config and make sure the following line is present.
-
-::
-
-    esi.so
-
-2. There are four options you can add to the above. 
-
-- "--private-response" will add private cache control and expires header to the processed ESI document. 
-- "--packed-node-support" will enable the support for using packed node, which will improve the performance of parsing
-  cached ESI document. 
-- "--disable-gzip-output" will disable gzipped output, which will NOT gzip the output anyway.
-- "--first-byte-flush" will enable the first byte flush feature, which will flush content to users as soon as the entire
-  ESI document is received and parsed without all ESI includes fetched (the flushing will stop at the ESI include markup
-  till that include is fetched). 
-
-3. We need a mapping for origin server response that contains the ESI markup. Assume that the ATS server is abc.com. And your origin server is xyz.com and the response containing ESI markup is http://xyz.com/esi.php. We will need
-   the following line in /usr/local/etc/trafficserver/remap.config
-
-::
-
-    map http://abc.com/esi.php http://xyz.com/esi.php
-
-4. Your response should contain ESI markup and a response header of 'X-Esi: 1'. e.g. using PHP,
-
-::
-
-    <?php   header('X-Esi: 1'); ?>
-    <html>
-    <body>
-    Hello, <esi:include src="http://abc.com/date.php"/>
-    </body>
-    </html>
-
-5. You will need a mapping for the src of the ESI include in remap.config if it is not already present.
-
-::
-
-    map http://abc.com/date.php http://xyz.com/date.php
-
-Or if both your ESI response and the ESI include comes from the same origin server, you can have the following line in
-remap.config instead to replace separate map rules for date.php and esi.php
-
-::
-
-    map http://abc.com/ http://xyz.com/
-
-6. Here is a sample PHP for date.php
-
-::
-
-    <?php
-    header ("Cache-control: no-cache");
-    echo date('l jS \of F Y h:i:s A');
-    ?>
-
-Useful Note
-===========
-
-1. You can provide proper cache control header and the ESI response and ESI include response can be cached separately.
-   It is extremely useful for rendering page with multiple modules. The page layout can be a ESI response with multiple
-   ESI include include, each for different module. The page layour ESI response can be cached and each individual ESI
-   include can also be cached with different duration. 
-
-2. You might want to compile the code without using ESI_PACKED_NODE_SUPPORT because it may not work in some corner cases
-
-Differences from Spec - http://www.w3.org/TR/esi-lang
-=====================================================
-
-1. <esi:include> does not support "alt" and "onerror" attributes
-
-2. <esi:inline> is not supported
-
-3. You cannot have <esi:try> inside another <esi:try>
-
-4. HTTP_USER_AGENT variable is not supported
-
-5. HTTP_COOKIE supports fetching for sub-key

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/generator.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/generator.en.rst b/doc/reference/plugins/generator.en.rst
deleted file mode 100644
index 28fadb3..0000000
--- a/doc/reference/plugins/generator.en.rst
+++ /dev/null
@@ -1,69 +0,0 @@
-.. _generator-plugin:
-
-Generator 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
-  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 `Generator` allows testing of synthetic workloads by generating
-HTTP responses of various sizes. The size and cacheability of the
-response is specified by the first two coomponents of the requested
-URL path. This plugin only supports the ``GET`` and ``HEAD`` HTTP
-methods.
-
-+---------------+----------------------------------------------------------------+
-|Path component | Description                                                    |
-+===============+================================================================+
-|1              | ``cache`` or ``nocache``. If ``cache`` is specifed, the        |
-|               | `Generator` plugin will respond with ``Cache-Control`` headers |
-|               | marking the response as cacheable for 24 hours.                |
-|2              | Integral number of bytes to return in the response.            |
-+---------------+----------------------------------------------------------------+
-
-Path components after the first 2 are ignored. This means that the
-trailing path components can be manipulated to create unique URLs
-following any covenient convention.
-
-The `Generator` plugin publishes the following metrics:
-
-  generator.response_bytes:
-    The total number of bytes emitted
-  generator.response_count:
-    The number of HTTP responses generated by the plugin
-
-Examples:
----------
-
-The most common way to use the `Generator` plugin is to configure
-it as a remap plugin in :file:`remap.config`::
-
-  map http://workload.example.com/ http://127.0.0.1/ \
-    @plugin=generator.so
-
-Notice that although the remap target is never contacted because
-the `Generator` plugin intercepts the request and acts as the origin
-server, it must be syntactically valid and resolvable in DNS.
-
-A 10 byte, cacheable object can then be generated::
-
-  $ curl -o /dev/null -x 127.0.0.1:8080 http://workload.example.com/cache/10/caf1fc92332b3a3c8cb8b3826b6a1658
-
-The `Generator` plugin can return responses as large as you like::
-
-  $ curl -o /dev/null -x 127.0.0.1:8080 http://workload.example.com/cache/$((10 * 1024 * 1024))/$RANDOM
-

http://git-wip-us.apache.org/repos/asf/trafficserver/blob/ce162a6d/doc/reference/plugins/geoip_acl.en.rst
----------------------------------------------------------------------
diff --git a/doc/reference/plugins/geoip_acl.en.rst b/doc/reference/plugins/geoip_acl.en.rst
deleted file mode 100644
index 15b46ad..0000000
--- a/doc/reference/plugins/geoip_acl.en.rst
+++ /dev/null
@@ -1,96 +0,0 @@
-.. _geoip-acl-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
-  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 is a simple ATS plugin for denying (or allowing) requests based on
-the source IP geo-location. Currently only the Maxmind APIs are
-supported, but we'd be happy to other other (open) APIs if you let us
-know. This plugin comes with the standard distribution of Apache Traffic
-Server, and should be installed as part of the normal build process.
-
-
-Configuration
-=============
-
-Once installed, there are three primary use cases, which we will discuss
-in details. Note that in all configurations, the first plugin parameter
-must specify what the matches should be applied to. Currently, only one
-rule set is supported, for Country ISO codes. This is specified with a
-parameter of ::
-
-    @pparam=country
-
-Future additions to this plugin could include other regions, such as
-city, state, continent etc.
-
-The three typical use cases are as follows:
-
-1. Per remap configurations, applicable to the entire remap rule. This
-   is useful when you can partition your content so that entire prefix
-   paths should be filtered. For example, lets assume that
-   http://example.com/music is restricted to US customers only, and
-   everything else is world wide accessible. In remap.config, you would
-   have something like ::
-
-    map http://example.com/music http://music.example.com \
-      @plugin=geoip_acl.so @pparam=country @pparam=allow @pparam=US
-    map http://example.com http://other.example.com
-
-2. If you can not partition the data with a path prefix, you can specify
-   a separate regex mapping filter. The remap.config file might then
-   look like ::
-
-    map http://example.com http://music.example.com \
-      @plugin=geoip_acl.so @pparam=country \
-      @pparam=regex::/etc/music.regex
-
-where music.regex is a format with PCRE (perl compatible) regular
-expressions, and unique rules for match. E.g.::
-
-    .*\.mp3  allow  US
-    .*\.ogg  deny   US
-
-Note that the default in the case of no matches on the regular
-expressions is to "allow" the request. This can be overriden, see next
-use case.
-
-3. You can also combine 1) and 2), and provide defaults in the
-   remap.config configuration, which then applies for the cases where no
-   regular expressions matches at all. This would be useful to override
-   the default which is to allow all requests that don't match. For
-   example ::
-
-    map http://example.com http://music.example.com \
-      @plugin=geoip_acl.so @pparam=country @pparam=allow @pparam= US
-      @pparam=regex::/etc/music.regex
-
-This tells the plugin that in the situation where there is no matching
-regular expression, only allow requests originating from the US.
-
-Finally, there's one additional parameter option that can be used ::
-
-    @pparam=html::/some/path.html
-
-This will override the default reponse body for the denied responses
-with a custom piece of HTML. This can be useful to explain to your users
-why they are getting denied access to a particular piece of content.
-This configuration can be used with any of the use cases described
-above.


Mime
View raw message