You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ig...@apache.org on 2013/04/18 11:57:08 UTC
[24/25] git commit: images moved
images moved
Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/0df18bfa
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/0df18bfa
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/0df18bfa
Branch: refs/heads/sphinx-docs
Commit: 0df18bfaea8bef0734019387b90aa3cbbd197aa0
Parents: 2bd2a2a
Author: Igor Galić <i....@brainsware.org>
Authored: Tue Mar 26 18:07:37 2013 +0100
Committer: Igor Galić <i....@brainsware.org>
Committed: Tue Mar 26 18:07:37 2013 +0100
----------------------------------------------------------------------
doc/source/admin/configuring-traffic-server.en.rst | 2 +-
doc/source/admin/hierachical-caching.en.rst | 2 +-
doc/source/admin/http-proxy-caching.en.rst | 4 ++--
doc/source/admin/index.en.rst | 2 +-
.../admin/reverse-proxy-http-redirects.en.rst | 4 ++--
doc/source/admin/security-options.en.rst | 4 ++--
doc/source/admin/transparent-proxy.en.rst | 2 +-
doc/source/admin/transparent-proxy/bridge.en.rst | 2 +-
.../transparent-proxy/wccp-configuration.en.rst | 4 ++--
doc/source/admin/working-log-files.en.rst | 2 +-
.../admin/working-log-files/log-formats.en.rst | 8 ++++----
11 files changed, 18 insertions(+), 18 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/configuring-traffic-server.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/configuring-traffic-server.en.rst b/doc/source/admin/configuring-traffic-server.en.rst
index 3afc8bb..93bf985 100644
--- a/doc/source/admin/configuring-traffic-server.en.rst
+++ b/doc/source/admin/configuring-traffic-server.en.rst
@@ -75,7 +75,7 @@ to apply some of the configuration changes.
The following is a sample portion of the
```records.config`` <../configuration-files/records.config>`_ file:
-.. figure:: _static/images/admin/records.jpg
+.. figure:: ../_static/images/admin/records.jpg
:align: center
:alt: Sample records.config file
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/hierachical-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/hierachical-caching.en.rst b/doc/source/admin/hierachical-caching.en.rst
index beaf6f7..fc0236a 100644
--- a/doc/source/admin/hierachical-caching.en.rst
+++ b/doc/source/admin/hierachical-caching.en.rst
@@ -64,7 +64,7 @@ cached and then served to the client. Future requests for this content
can now be served directly from the Traffic Server cache (until the data
is stale or expired).
-.. figure:: _static/images/admin/cachehrc.jpg
+.. figure:: ../_static/images/admin/cachehrc.jpg
:align: center
:alt: Parent caching
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/http-proxy-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/http-proxy-caching.en.rst b/doc/source/admin/http-proxy-caching.en.rst
index 3a9fc14..c602742 100644
--- a/doc/source/admin/http-proxy-caching.en.rst
+++ b/doc/source/admin/http-proxy-caching.en.rst
@@ -51,7 +51,7 @@ overview illustrates how Traffic Server serves a request.
Server serves it to the client as a **cache hit** (see the figure
below).
- .. figure:: _static/images/admin/cache_hit.jpg
+ .. figure:: ../_static/images/admin/cache_hit.jpg
:align: center
:alt: A cache hit
@@ -68,7 +68,7 @@ overview illustrates how Traffic Server serves a request.
cache (see the figure below). Subsequent requests for the object can
be served faster because the object is retrieved directly from cache.
- .. figure:: _static/images/admin/cache_miss.jpg
+ .. figure:: ../_static/images/admin/cache_miss.jpg
:align: center
:alt: A cache miss
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/index.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/index.en.rst b/doc/source/admin/index.en.rst
index 3032832..d959287 100644
--- a/doc/source/admin/index.en.rst
+++ b/doc/source/admin/index.en.rst
@@ -224,7 +224,7 @@ processes are described below:
The figure below illustrates the three Traffic Server processes.
-.. figure:: _static/images/admin/process.jpg
+.. figure:: ../_static/images/admin/process.jpg
:align: center
:alt: Illustration of the three Traffic Server Processes
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/reverse-proxy-http-redirects.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/reverse-proxy-http-redirects.en.rst b/doc/source/admin/reverse-proxy-http-redirects.en.rst
index 27db562..babe751 100644
--- a/doc/source/admin/reverse-proxy-http-redirects.en.rst
+++ b/doc/source/admin/reverse-proxy-http-redirects.en.rst
@@ -69,7 +69,7 @@ less-reliable PC origin servers as backup servers. In fact, a single
Traffic Server can act as the virtual origin server for multiple backup
origin servers, as shown in the figure below.
-.. figure:: _static/images/admin/revproxy.jpg
+.. figure:: ../_static/images/admin/revproxy.jpg
:align: center
:alt: Traffic Server as reverse proxy for a pair of origin servers
@@ -129,7 +129,7 @@ In reverse proxy mode, Traffic Server serves HTTP requests on behalf of
a web server. The figure below illustrates how Traffic Server in reverse
proxy mode serves an HTTP request from a client browser.
-.. figure:: _static/images/admin/httprvs.jpg
+.. figure:: ../_static/images/admin/httprvs.jpg
:align: center
:alt: HTTP reverse proxy
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/security-options.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/security-options.en.rst b/doc/source/admin/security-options.en.rst
index 88b933c..fd00052 100644
--- a/doc/source/admin/security-options.en.rst
+++ b/doc/source/admin/security-options.en.rst
@@ -95,7 +95,7 @@ Server (and between Traffic Server and an origin server) when the SSL
termination option is enabled & configured for\ *\* client/Traffic
Server connections only*\ \*.
-.. figure:: _static/images/admin/ssl_c.jpg
+.. figure:: ../_static/images/admin/ssl_c.jpg
:align: center
:alt: Client and Traffic Server communication using SSL termination
@@ -179,7 +179,7 @@ The figure below illustrates communication between Traffic Server and an
origin server when the SSL termination option is enabled for **Traffic
Server/origin server connections**.
-.. figure:: _static/images/admin/ssl_os.jpg
+.. figure:: ../_static/images/admin/ssl_os.jpg
:align: center
:alt: Traffic Server and origin server communication using SSL termination
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/transparent-proxy.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/transparent-proxy.en.rst b/doc/source/admin/transparent-proxy.en.rst
index dacbd8c..2e969dd 100644
--- a/doc/source/admin/transparent-proxy.en.rst
+++ b/doc/source/admin/transparent-proxy.en.rst
@@ -34,7 +34,7 @@ intercept connections between clients and servers without being visible.
The general network structure that will be used in this documentation
looks like this --
-.. figure:: _static/images/admin/ats-basic-traffic.png
+.. figure:: ../_static/images/admin/ats-basic-traffic.png
:align: center
:alt: ATS basic traffic flow of Transparent Proxy
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/transparent-proxy/bridge.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/transparent-proxy/bridge.en.rst b/doc/source/admin/transparent-proxy/bridge.en.rst
index 198aef5..4cdf829 100644
--- a/doc/source/admin/transparent-proxy/bridge.en.rst
+++ b/doc/source/admin/transparent-proxy/bridge.en.rst
@@ -62,7 +62,7 @@ bridge is functional.
Once the bridge is verified to work, this is the basic traffic pattern
of interest.
-.. figure:: ../_static/images/admin/ats-traffic-bridge.png
+.. figure:: ../../_static/images/admin/ats-traffic-bridge.png
:align: center
:alt: Picture of traffic flow through a bridge with ATS
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/transparent-proxy/wccp-configuration.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/transparent-proxy/wccp-configuration.en.rst b/doc/source/admin/transparent-proxy/wccp-configuration.en.rst
index d139025..7984865 100644
--- a/doc/source/admin/transparent-proxy/wccp-configuration.en.rst
+++ b/doc/source/admin/transparent-proxy/wccp-configuration.en.rst
@@ -150,6 +150,6 @@ References
This is not fundamentally impossible, as the packets are distinct in
layer
-.. |important| image:: ../_static/images/docbook/important.png
-.. |image1| image:: ../_static/images/docbook/important.png
+.. |important| image:: ../../_static/images/docbook/important.png
+.. |image1| image:: ../../_static/images/docbook/important.png
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/working-log-files.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/working-log-files.en.rst b/doc/source/admin/working-log-files.en.rst
index 500d2bb..634b379 100644
--- a/doc/source/admin/working-log-files.en.rst
+++ b/doc/source/admin/working-log-files.en.rst
@@ -810,7 +810,7 @@ log collation server receives a log buffer from a client, it writes it
to its own log file as if it was generated locally. For a visual
representation of this, see the figure below.
-.. figure:: _static/images/admin/logcolat.jpg
+.. figure:: ../_static/images/admin/logcolat.jpg
:align: center
:alt: Log collation
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/0df18bfa/doc/source/admin/working-log-files/log-formats.en.rst
----------------------------------------------------------------------
diff --git a/doc/source/admin/working-log-files/log-formats.en.rst b/doc/source/admin/working-log-files/log-formats.en.rst
index 35a8565..5735beb 100644
--- a/doc/source/admin/working-log-files/log-formats.en.rst
+++ b/doc/source/admin/working-log-files/log-formats.en.rst
@@ -83,7 +83,7 @@ Squid Format
The following figure shows a sample log entry in a ``squid.log`` file.
-.. figure:: ../_static/images/admin/squid_format.jpg
+.. figure:: ../../_static/images/admin/squid_format.jpg
:align: center
:alt: Sample log entry in squid.log
@@ -213,7 +213,7 @@ Netscape Common
The following figure shows a sample log entry in a ``common.log`` file,
the list following describes the fields of the format.
-.. figure:: ../_static/images/admin/netscape_common_format.jpg
+.. figure:: ../../_static/images/admin/netscape_common_format.jpg
:align: center
:alt: Sample log entry in common.log
@@ -235,7 +235,7 @@ Netscape Extended
The following figure shows a sample log entry in an ``extended.log``
file.
-.. figure:: ../_static/images/admin/netscape_extended_format.jpg
+.. figure:: ../../_static/images/admin/netscape_extended_format.jpg
:align: center
:alt: sample log entry in extended.log
@@ -258,7 +258,7 @@ Netscape Extended2
The following figure shows a sample log entry in an ``extended2.log``
file.
-.. figure:: ../_static/images/admin/netscape_extended2_format.jpg
+.. figure:: ../../_static/images/admin/netscape_extended2_format.jpg
:align: center
:alt: sample log entry in extended2.log