You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/07/02 04:05:05 UTC

[jira] [Updated] (TS-3704) fix broken links during "make html" part 2

     [ https://issues.apache.org/jira/browse/TS-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-3704:
------------------------------
    Fix Version/s: Docs

> fix broken links during "make html" part 2
> ------------------------------------------
>
>                 Key: TS-3704
>                 URL: https://issues.apache.org/jira/browse/TS-3704
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Docs
>            Reporter: Oknet Xu
>             Fix For: Docs
>
>
> here is the patch:
> {code}
> diff --git a/doc/arch/cache/cache-arch.en.rst b/doc/arch/cache/cache-arch.en.rst
> index b870a88..6b36347 100644
> --- a/doc/arch/cache/cache-arch.en.rst
> +++ b/doc/arch/cache/cache-arch.en.rst
> @@ -36,7 +36,7 @@ discussed only to the extent needed to understand the internal mechanisms. This
>  document will be useful primarily to |TS| developers working on the |TS|
>  codebase or plugins for |TS|. It is assumed the reader is already familiar with
>  the :ref:`admin-guide` and specifically with :ref:`http-proxy-caching` and
> -:ref:`configuring-the-cache` along with the associated configuration files and
> +:ref:`admin-configuring-the-cache` along with the associated configuration files and
>  values.
>  
>  Unfortunately, the internal terminology is not particularly consistent, so this
> @@ -789,7 +789,7 @@ information. This will always contain the HTTP headers for all
>     There is provision in the code to support *read while write*, that is,
>     serving an object from cache in one transaction while it is being written in
>     another. Several settings are needed for it to be used. See
> -   :ref:`reducing-origin-server-requests-avoiding-the-thundering-herd`. It must
> +   :ref:`admin-reducing-origin-server-requests`. It must
>     specifically enabled in :file:`records.config` and if not, a cache read will
>     fail if the object is currently be written or updated.
>  
> diff --git a/doc/reference/commands/traffic_server.en.rst b/doc/reference/commands/traffic_server.en.rst
> index abbee2a..75c11ea 100644
> --- a/doc/reference/commands/traffic_server.en.rst
> +++ b/doc/reference/commands/traffic_server.en.rst
> @@ -15,7 +15,7 @@
>    specific language governing permissions and limitations
>    under the License.
>  
> -.. _traffic-server:
> +.. _traffic_server:
>  
>  ==============
>  traffic_server
> diff --git a/doc/reference/commands/traffic_via.en.rst b/doc/reference/commands/traffic_via.en.rst
> index 94a82fd..26aa057 100644
> --- a/doc/reference/commands/traffic_via.en.rst
> +++ b/doc/reference/commands/traffic_via.en.rst
> @@ -71,7 +71,7 @@ Decode the Via header from command-line arguments::
>      Parent proxy connection status                         :no parent proxy or unknown
>      Origin server connection status                        :connection open failed
>  
> -Decode the Via header from a curl request, using the :ref:`X-Debug <_xdebug_plugin>` plugin::
> +Decode the Via header from a curl request, using the :ref:`X-Debug <xdebug_plugin>` plugin::
>  
>      $ curl -H  "X-Debug: Via" -I http://test.example.com | traffic_via -
>      Via header is uScMsSf pSeN:t cCMi p sS, Length is 24
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)