You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ig...@apache.org on 2013/07/10 02:32:54 UTC
git commit: attempt to fix links in admin guide
Updated Branches:
refs/heads/master 231274cf9 -> 492553949
attempt to fix links in admin guide
I think what we'll end up doing here will simply be a collection of all
our links, thematically ordered, in a single file and include them.
Right now, this still doesn't work out perfectly, because it depends on
multiviews (or some form of negotiation). But otherwise, links to
*.config work.
Deeplinks into records.config don't work yet, because that file's a mess
Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/49255394
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/49255394
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/49255394
Branch: refs/heads/master
Commit: 492553949947213836fa28fc900a5095f5ce1c23
Parents: 231274c
Author: Igor Galić <i....@brainsware.org>
Authored: Wed Jul 10 02:29:04 2013 +0200
Committer: Igor Galić <i....@brainsware.org>
Committed: Wed Jul 10 02:32:21 2013 +0200
----------------------------------------------------------------------
doc/admin/http-proxy-caching.en.rst | 216 +++++++++++++++----------------
1 file changed, 104 insertions(+), 112 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/49255394/doc/admin/http-proxy-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/http-proxy-caching.en.rst b/doc/admin/http-proxy-caching.en.rst
index e8b5bc7..b5e8153 100644
--- a/doc/admin/http-proxy-caching.en.rst
+++ b/doc/admin/http-proxy-caching.en.rst
@@ -115,8 +115,8 @@ by:
::
freshness_limit = ( date - last_modified ) * 0.10
- where *``date``* is the date in the object's server response header
- and *``last_modified``* is the date in the ``Last-Modified`` header.
+ where *date* is the date in the object's server response header
+ and *last_modified* is the date in the ``Last-Modified`` header.
If there is no ``Last-Modified`` header, then Traffic Server uses the
date the object was written to cache. The value ``0.10`` (10 percent)
can be increased or reduced to better suit your needs (refer to
@@ -124,24 +124,21 @@ by:
Computations <#ModifyingAgingFactorFreshnessComputations>`_).
The computed freshness limit is bound by a minimum and maximum value
- - refer to `Setting an Absolute Freshness
- Limit <#SettingAbsoluteFreshnessLimit>`_ for more information.
+ - refer to `Setting an Absolute Freshness Limit`_ for more information.
- **Checking the absolute freshness limit**
For HTTP objects that do not have ``Expires`` headers or do not have
both ``Last-Modified`` and ``Date`` headers, Traffic Server uses a
- maximum and minimum freshness limit (refer to `Setting an Absolute
- Freshness Limit <#SettingAbsoluteFreshnessLimit>`_).
+ maximum and minimum freshness limit (refer to `Setting an Absolute Freshness Limit`_).
-- **Checking revalidate rules in the ``cache.config`` file**
+- **Checking revalidate rules in the `cache.config`_ file**
Revalidate rules apply freshness limits to specific HTTP objects. You
can set freshness limits for objects originating from particular
domains or IP addresses, objects with URLs that contain specified
regular expressions, objects requested by particular clients, and so
- on (refer to
- ```cache.config`` <../configuration-files/cache.config>`_).
+ on (refer to `cache.config`_).
Modifying Aging Factor for Freshness Computations
-------------------------------------------------
@@ -154,10 +151,9 @@ the percentage according to your needs.
To modify the aging factor for freshness computations
-1. Edit the following variables in
- ```records.config`` <../configuration-files/records.config>`_
+1. Edit the following variables in `records.config`_
- - `*``proxy.config.http.cache.heuristic_lm_factor``* <configuration-files/records.config#proxy.config.http.cache.heuristic_lm_factor>`_
+ - `proxy.config.http.cache.heuristic_lm_factor`_
2. Run the ``traffic_line -x`` command to apply the configuration
changes.
@@ -172,11 +168,10 @@ freshness limit**.
To specify an absolute freshness limit
-1. Edit the following variables in
- ```records.config`` <../configuration-files/records.config>`_
+1. Edit the following variables in `records.config`_
- - `*``proxy.config.http.cache.heuristic_min_lifetime``* <configuration-files/records.config#proxy.config.http.cache.heuristic_min_lifetime>`_
- - `*``proxy.config.http.cache.heuristic_max_lifetime``* <configuration-files/records.config#proxy.config.http.cache.heuristic_max_lifetime>`_
+ - `proxy.config.http.cache.heuristic_min_lifetime`_
+ - `proxy.config.http.cache.heuristic_max_lifetime`_
2. Run the ``traffic_line -x`` command to apply the configuration
changes.
@@ -195,10 +190,9 @@ information).
To configure Traffic Server to cache objects with specific headers
-1. Edit the following variable in
- ```records.config`` <../configuration-files/records.config>`_
+1. Edit the following variable in `records.config`_
- - `*``proxy.config.http.cache.required_headers``* <configuration-files/records.config#proxy.config.http.cache.required_headers>`_
+ - `proxy.config.http.cache.required_headers`_
2. Run the ``traffic_line -x`` command to apply the configuration
changes.
@@ -219,8 +213,7 @@ affect whether objects are served from cache:
it should not to serve any objects directly from the cache;
therefore, Traffic Server will always obtain the object from the
origin server. You can configure Traffic Server to ignore client
- ``no-cache`` headers - refer to `Configuring Traffic Server to Ignore
- Client no-cache Headers <#ConfiguringTSIgnoreClientnocacheHeaders>`_
+ ``no-cache`` headers - refer to `Configuring Traffic Server to Ignore Client no-cache Headers`_
for more information.
- The ``max-age`` header, sent by servers, is compared to the object
@@ -267,8 +260,8 @@ revalidation is one of the following:
By default, Traffic Server revalidates a requested HTTP object in the
cache if it considers the object to be stale. Traffic Server evaluates
-object freshness as described in `HTTP Object
-Freshness <#HTTPObjectFreshness>`_. You can reconfigure how Traffic
+object freshness as described in `HTTP Object Freshness`_.
+You can reconfigure how Traffic
Server evaluates freshness by selecting one of the following options:
- Traffic Server considers all HTTP objects in the cache to be stale:
@@ -280,15 +273,13 @@ Server evaluates freshness by selecting one of the following options:
without ``Expires`` or ``Cache-Control`` headers.
To configure how Traffic Server revalidates objects in the cache, you
-can set specific revalidation rules in
-```cache.config`` <../configuration-files/records.config>`_.
+can set specific revalidation rules in `cache.config`_.
To configure revalidation options
-1. Edit the following variable in
- ```records.config`` <../configuration-files/records.config>`_
+1. Edit the following variable in `records.config`_
- - `*``proxy.config.http.cache.when_to_revalidate``* <configuration-files/records.config#proxy.config.http.cache.when_to_revalidate>`_
+ - `proxy.config.http.cache.when_to_revalidate`_
2. Run the ``traffic_line -x`` command to apply the configuration
changes.
@@ -325,23 +316,21 @@ performance of this feature.
Traffic Server also provides a **Force Immediate Update** option that
enables you to update URLs immediately without waiting for the specified
update time to occur. You can use this option to test your scheduled
-update configuration (refer to `Forcing an Immediate
-Update <#ForcingImmediateUpdate>`_).
+update configuration (refer to `Forcing an Immediate Update`_).
Configuring the Scheduled Update Option
---------------------------------------
To configure the scheduled update option
-1. Edit ```update.config`` <../configuration-files/update.config>`_ to
+1. Edit `update.config`_ to
enter a line in the file for each URL you want to update.
-2. Edit the following variables in
- ```records.config`` <../configuration-files/records.config>`_
+2. Edit the following variables in `records.config`_
- - `*``proxy.config.update.enabled``* <configuration-files/records.config#proxy.config.http.update.enabled>`_
- - `*``proxy.config.update.retry_count``* <configuration-files/records.config#proxy.config.http.update.retry_count>`_
- - `*``proxy.config.update.retry_interval``* <configuration-files/records.config#proxy.config.http.update.retry_interval>`_
- - `*``proxy.config.update.concurrent_updates``* <configuration-files/records.config#proxy.config.http.update.concurrent_updates>`_
+ - `proxy.config.update.enabled`_
+ - `proxy.config.update.retry_count`_
+ - `proxy.config.update.retry_interval`_
+ - `proxy.config.update.concurrent_updates`_
3. Run the ``traffic_line -x`` command to apply the configuration
changes.
@@ -350,30 +339,27 @@ Forcing an Immediate Update
---------------------------
Traffic Server provides a **Force Immediate Update** option that enables
-you to immediately verify the URLs listed in the ``update.config`` file.
+you to immediately verify the URLs listed in the `update.config`_ file.
The Force Immediate Update option disregards the offset hour and
-interval set in the ``update.config`` file and immediately updates the
+interval set in the `update.config`_ file and immediately updates the
URLs listed.
To configure the Force Immediate Update option
-1. Edit the following variables in
- ```records.config`` <../configuration-files/records.config>`_
+1. Edit the following variables in `records.config`_
- - `*``proxy.config.update.force``* <configuration-files/records.config#proxy.config.http.update.force>`_
+ - `proxy.config.update.force`_
- Make sure the variable
- `*``proxy.config.update.enabled``* <configuration-files/records.config#proxy.config.http.update.enabled>`_
- is set to 1.
+ `proxy.config.update.enabled`_ is set to 1.
2. Run the ``command traffic_line -x`` to apply the configuration
changes.
**IMPORTANT:** When you enable the Force Immediate Update option,
Traffic Server continually updates the URLs specified in the
-``update.config`` file until you disable the option. To disable the
+`update.config`_ file until you disable the option. To disable the
Force Immediate Update option, set the variable
-`*``proxy.config.update.force``* <configuration-files/records.config#proxy.config.http.update.force>`_
-to ``0`` (zero).
+`proxy.config.update.force`_ to ``0`` (zero).
Pushing Content into the Cache
==============================
@@ -390,16 +376,14 @@ must configure Traffic Server to accept ``PUSH`` requests.
To configure Traffic Server to accept ``PUSH`` requests
-1. Edit ```records.config`` <../configuration-files/records.config>`_,
- modify the super mask to allow ``PUSH`` request.
+1. Edit `records.config`_, modify the super mask to allow ``PUSH`` request.
- - `*``proxy.config.http.quick_filter.mask``* <configuration-files/records.config#proxy.config.http.quick_filter.mask>`_
+ - `proxy.config.http.quick_filter.mask`_
-2. Edit the following variable in
- ```records.config`` <../configuration-files/records.config>`_, enable
+2. Edit the following variable in `records.config`_, enable
the push_method.
- - `*``proxy.config.http.push_method_enabled``* <configuration-files/records.config#proxy.config.http.push_method_enabled>`_
+ - `proxy.config.http.push_method_enabled`_
3. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -430,8 +414,7 @@ place in the cache. The following is an example of a ``PUSH`` request:
Tools that will help manage pushing
-----------------------------------
-There is a perl script for pushing,
-```tools/push.pl`` <http://git-wip-us.apache.org/repos/asf?p=trafficserver.git;a=blob;f=tools/push.pl>`_,
+There is a perl script for pushing, `tools/push.pl`_,
which can help you understanding how to write some script for pushing
content.
@@ -447,13 +430,11 @@ if it is indeed cacheable.
To set cache pinning rules
-3. Make sure the following variable in
- ```records.config`` <../configuration-files/records.config>`_ is set
+3. Make sure the following variable in `records.config`_ is set
- - `*``proxy.config.cache.permit.pinning``* <configuration-files/records.config#proxy.config.cache.permit.pinning>`_
+ - `proxy.config.cache.permit.pinning`_
-4. Add a rule in
- ```cache.config`` <../configuration-files/cache.config>`_ for each
+4. Add a rule in `cache.config`_ for each
URL you want Traffic Server to pin in the cache. For example:
::
@@ -492,8 +473,7 @@ By default, Traffic Server does *not* cache objects with the following
- ``Cache-Control: no-cache`` header
To configure Traffic Server to ignore the ``Cache-Control: no-cache``
- header, refer to `Configuring Traffic Server to Ignore Client
- no-cache Headers <#ConfiguringTSIgnoreClientnocacheHeaders>`_.
+ header, refer to `Configuring Traffic Server to Ignore Client no-cache Headers`_
- ``Cookie``: header (for text objects)
@@ -501,8 +481,7 @@ By default, Traffic Server does *not* cache objects with the following
requests that contain cookies (unless the object is text). You can
configure Traffic Server to not cache cookied content of any type,
cache all cookied content, or cache cookied content that is of image
- type only. For more information, refer to `Caching Cookied
- Objects <#CachingCookiedObjects>`_.
+ type only. For more information, refer to `Caching Cookied Objects`_.
Configuring Traffic Server to Ignore Client no-cache Headers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -517,10 +496,9 @@ from its cache.
To configure Traffic Server to ignore client ``no-cache`` headers
-3. Edit the following variable in
- ```records.config`` <../configuration-files/records.config>`_
+3. Edit the following variable in `records.config`_
- - `*``proxy.config.cache.ignore_client_no_cache``* <configuration-files/records.config#proxy.config.cache.ignore_client_no_cache>`_
+ - `proxy.config.cache.ignore_client_no_cache`
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -535,16 +513,14 @@ By default, Traffic Server does *not* cache objects with the following
- ``Cache-Control: private`` header
- ``WWW-Authenticate``: header
- To configure Traffic Server to ignore\ ``WWW-Authenticate`` headers,
- refer to `Configuring Traffic Server to Ignore WWW-Authenticate
- Headers <#ConfiguringTrafficEdgeIgnoreWWWAuthenticateHeaders>`_.
+ To configure Traffic Server to ignore ``WWW-Authenticate`` headers,
+ refer to `Configuring Traffic Server to Ignore WWW-Authenticate Headers`_.
- ``Set-Cookie``: header
- ``Cache-Control: no-cache`` headers
To configure Traffic Server to ignore ``no-cache`` headers, refer to
- `Configuring Traffic Server to Ignore Server no-cache
- Headers <#ConfiguringTrafficEdgeIgnoreServerNoCacheHeaders>`_.
+ `Configuring Traffic Server to Ignore Server no-cache Headers`_.
- ``Expires``: header with value of 0 (zero) or a past date
@@ -561,10 +537,9 @@ appropriate in most cases.
To configure Traffic Server to ignore server ``no-cache`` headers
-3. Edit the following variable in
- ```records.config`` <../configuration-files/records.config>`_
+3. Edit the following variable in `records.config`_
- - `*``proxy.config.cache.ignore_server_no_cache``* <configuration-files/records.config#proxy.config.cache.ignore_server_no_cache>`_
+ - `proxy.config.cache.ignore_server_no_cache`_
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -588,10 +563,9 @@ about HTTP 1.1.
To configure Traffic Server to ignore server ``WWW-Authenticate``
headers
-3. Edit the following variable in
- ```records.config`` <../configuration-files/records.config>`_
+3. Edit the following variable in `records.config`_
- - `*``proxy.config.cache.ignore_authentication``* <configuration-files/records.config#proxy.config.cache.ignore_authentication>`_
+ - `proxy.config.cache.ignore_authentication`_
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -605,16 +579,13 @@ files.
You can configure Traffic Server to do the following:
-- *Not* cache any HTTP objects (refer to `Disabling HTTP Object
- Caching <#DisablingHTTPObjectCaching>`_).
+- *Not* cache any HTTP objects (refer to `Disabling HTTP Object Caching`_).
- Cache **dynamic content** - that is, objects with URLs that end in
**``.asp``** or contain a question mark (**``?``**), semicolon
- (**``;``**), or **``cgi``**. For more information, refer to `Caching
- Dynamic Content <#CachingDynamicContent>`_.
+ (**``;``**), or **``cgi``**. For more information, refer to `Caching Dynamic Content`_.
- Cache objects served in response to the ``Cookie:`` header (refer to
- `Caching Cookied Objects) <#CachingCookiedObjects>`_.
-- Observe ``never-cache`` rules in the
- ```cache.config`` <../configuration-files/cache.config>`_ file.
+ `Caching Cookied Objects`_.
+- Observe ``never-cache`` rules in the `cache.config`_ file.
Disabling HTTP Object Caching
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -628,10 +599,9 @@ directly from the origin server and never cached, as detailed below.
To disable HTTP object caching manually
-3. Edit the following variable in
- ```records.config`` <configuration-files/records.config>`_
+3. Edit the following variable in `records.config`_
- - `*``proxy.config.cache.http``* <configuration-files/records.config#proxy.config.cache.http>`_
+ - `proxy.config.cache.http`_
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -649,10 +619,9 @@ appropriate ``Cache-Control`` headers.
To configure Traffic Server's cache behaviour in regard to dynamic
content
-3. Edit the following variable in
- ```records.config`` <configuration-files/records.config>`_
+3. Edit the following variable in `records.config`_
- - `*``proxy.config.http.cache.cache_urls_that_look_dynamic``* <configuration-files/records.config#proxy.config.http.cache.cache_urls_that_look_dynamic>`_
+ - `proxy.config.http.cache.cache_urls_that_look_dynamic`
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -677,10 +646,9 @@ You can reconfigure Traffic Server to:
To configure how Traffic Server caches cookied content
-3. Edit the following variable in
- ```records.config`` <configuration-files/records.config>`_
+3. Edit the following variable in `records.config`_
- - `*``proxy.config.cache_responses_to_cookies``* <configuration-files/records.config#proxy.config.cache_responses_to_cookies>`_
+ - `proxy.config.cache_responses_to_cookies`_
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -695,7 +663,7 @@ headers.
To force document caching
1. Add a rule for each URL you want Traffic Server to pin to the cache
- ```cache.config`` <../configuration-files/cache.config>`_:
+ `cache.config`_:
::
url_regex=^https?://(www.)?apache.org/dev/ ttl-in-cache=6h
@@ -723,20 +691,19 @@ Configuring How Traffic Server Caches Alternates
To configure how Traffic Server caches alternates, follow the steps
below
-3. Edit the following variables in
- ```records.config`` <../configuration-files/records.config>`_
+3. Edit the following variables in `ecords.config`_
- - `*``proxy.config.http.cache.enable_default_vary_headers``* <configuration-files/records.config#proxy.config.http.cache.enable_default_vary_headers>`_
- - `*``proxy.config.http.cache.vary_default_text``* <configuration-files/records.config#proxy.config.http.cache.vary_default_text>`_
- - `*``proxy.config.http.cache.vary_default_images``* <configuration-files/records.config#proxy.config.cache.vary_default_images>`_
- - `*``proxy.config.http.cache.vary_default_other``* <configuration-files/records.config#proxy.config.http.cache.vary_default_other>`_
+ - `proxy.config.http.cache.enable_default_vary_headers`_
+ - `proxy.config.http.cache.vary_default_text`_
+ - `proxy.config.http.cache.vary_default_images`_
+ - `proxy.config.http.cache.vary_default_other`_
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
**Note:** If you specify ``Cookie`` as the header field on which to vary
in the above variables, make sure that the variable
-`*``proxy.config.cache.cache_responses_to_cookies``* <configuration-files/records.config#proxy.config.cache.cache_responses_to_cookies>`_
+`proxy.config.cache.cache_responses_to_cookies`
is set appropriately.
Limiting the Number of Alternates for an Object
@@ -752,10 +719,9 @@ scan sequentially through available alternates in the object store.
To limit the number of alternates
-3. Edit the following variable in
- ```records.config`` <../configuration-files/records.config>`_
+3. Edit the following variable in `records.config`_
- - `*``proxy.config.cache.limits.http.max_alts``* <configuration-files/records.config#proxy.config.cache.limits.http.max_alts>`_
+ - `proxy.config.cache.limits.http.max_alts`_
4. Run the command ``traffic_line -x`` to apply the configuration
changes.
@@ -771,15 +737,11 @@ retry the congested origin server later.
To use the **Congestion Control** option, you must perform the following
tasks:
-3. Set the following variable in
- ```records.config`` <configuration-files/records.config>`_
+3. Set the following variable in `records.config`_
- - `*``proxy.config.http.congestion_control.enabled``* <configuration-files/records.config#proxy.config.http.congestion_control.enabled>`_
- to ``1``
+ - `proxy.config.http.congestion_control.enabled`_ to ``1``
-- Create rules in the
- ```congestion.config`` <configuration-files/congestion.config>`_
- file to specify:
+- Create rules in the `congestion.config`_ file to specify:
- which origin servers Traffic Server tracks for congestion
- the timeouts Traffic Server uses, depending on whether a server is
congested
@@ -791,3 +753,33 @@ tasks:
9. Run the command ``traffic_line -x`` to apply the configuration
changes.
+
+.. List of links
+.. _records.config: configuration-files/records.config
+.. _cache.config: configuration-files/cache.config
+.. _congestion.config: configuration-files/congestion.config
+.. _proxy.config.http.congestion_control.enabled: configuration-files/records.config#proxy.config.http.congestion_control.enabled
+.. _proxy.config.cache.limits.http.max_alts: configuration-files/records.config#proxy.config.cache.limits.http.max_alts
+.. _proxy.config.http.cache.heuristic_lm_factor: configuration-files/records.config#proxy.config.http.cache.heuristic_lm_factor
+.. _proxy.config.http.cache.heuristic_min_lifetime: configuration-files/records.config#proxy.config.http.cache.heuristic_min_lifetime
+.. _proxy.config.http.cache.heuristic_max_lifetime: configuration-files/records.config#proxy.config.http.cache.heuristic_max_lifetime
+.. _proxy.config.http.cache.when_to_revalidate: configuration-files/records.config#proxy.config.http.cache.when_to_revalidate
+.. _proxy.config.update.enabled: configuration-files/records.config#proxy.config.update.enabled
+.. _proxy.config.update.retry_count: configuration-files/records.config#proxy.config.update.retry_count
+.. _proxy.config.update.concurrent_updates: configuration-files/records.config#proxy.config.update.concurrent_updates
+.. _proxy.config.update.force: configuration-files/records.config#proxy.config.update.force
+.. _proxy.config.http.quick_filter.mask: configuration-files/records.config#proxy.config.http.quick_filter.mask
+.. _proxy.config.http.push_method_enabled: configuration-files/records.config#proxy.config.http.push_method_enabled
+.. _proxy.config.cache.permit.pinning: configuration-files/records.config#proxy.config.cache.permit.pinning
+.. _proxy.config.cache.ignore_server_no_cache: configuration-files/records.config#proxy.config.cache.ignore_server_no_cache
+.. _proxy.config.cache.ignore_authentication: configuration-files/records.config#proxy.config.cache.ignore_authentication
+.. _proxy.config.cache.http: configuration-files/records.config#proxy.config.cache.http
+.. _proxy.config.http.cache.cache_urls_that_look_dynamic: configuration-files/records.config#proxy.config.http.cache.cache_urls_that_look_dynamic
+.. _proxy.config.cache_responses_to_cookies: configuration-files/records.config#proxy.config.cache_responses_to_cookies
+.. _proxy.config.http.cache.enable_default_vary_headers: configuration-files/records.config#proxy.config.http.cache.enable_default_vary_headers
+.. _proxy.config.http.cache.vary_default_text: configuration-files/records.config#proxy.config.http.cache.vary_default_text
+.. _proxy.config.http.cache.vary_default_images: configuration-files/records.config#proxy.config.http.cache.vary_default_images
+.. _proxy.config.http.cache.vary_default_other: configuration-files/records.config#proxy.config.http.cache.vary_default_other
+.. _proxy.config.cache.cache_responses_to_cookies: configuration-files/records.config#proxy.config.cache.cache_responses_to_cookies
+
+.. _tools/push.pl: http://git-wip-us.apache.org/repos/asf?p=trafficserver.git;a=blob;f=tools/push.pl