svn commit: r790310 - in /websites/staging/trafficserver/trunk/content/docs/trunk: STATUS admin/explicit-proxy-caching/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 31 23:42:49 2011
New Revision: 790310

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/STATUS
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/explicit-proxy-caching/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/STATUS
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/STATUS (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/STATUS Tue May 31 23:42:49 2011
@@ -9,10 +9,6 @@ Documentation Project, please see (LINK)
 To Do List
 =======================
 
-- migrate CSS and pictures
-
-- integrate multi-language link generation
-
 - integrate navigation/TOC generation
 
 - invent a wheel that will help translators and users spot out-dated documents
@@ -42,18 +38,7 @@ Migration procedure
 
 Content Migration
 =======================
-- SDK is done.
-
-- admin guide was just migrated automatically, so we have a strating point
-  it needs to be cleaned up.
-
-- Admin Guide, like SDK, has been broken up in directories.
-  Their names corresponding to chapter names.
-  The idea is that this makes adding translations more managable, but
-  also has the potential to break up big pages of the admin guide into smaller easier
-  digestable ones. In particular: files.htm *grrrrrr*
-
-
+- SDK and Admin is done.
 
 Findings
 =================
@@ -62,4 +47,52 @@ Findings
 
 - Make sure to put pictures in their own pragraph.
 
-- **`foo\_bar`** -- while this is very ugly, it makes the document redable with Vim's Markdown syntax ;)
+
+Collision avoidance
+=====================
+
+Keep this section updated, when you start out to work on a chapter.
+
+Admin Guide:
+------------
+index - done
+getting-started - done
+http-proxy-caching - done
+reverse-proxy-http-redirects - done
+explicit-proxy-caching - done
+hierachical-caching
+configuring-cache
+monitoring-traffic
+configuring-traffic-server
+cluster-howto
+security-options
+working-log-files
+traffic-line-commands
+event-logging-formats
+configuration-files
+traffic-server-error-messages
+faqs
+plugins
+
+SDK Docs:
+------------
+index
+preface
+getting-started
+how-to-create-trafficserver-plugins
+remap-plugin
+header-based-plugin-examples
+http-transformation-plugin
+new-protocol-plugins
+http-hooks-and-transactions
+misc-interface-guide
+http-headers
+mutex-guide
+continuations
+plugin-configurations
+actions-guide
+io-guide
+plugin-management
+adding-statistics
+sample-source-code
+troubleshooting-tips

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/explicit-proxy-caching/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/explicit-proxy-caching/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/explicit-proxy-caching/index.en.html Tue May 31 23:42:49 2011
@@ -39,17 +39,26 @@
   <div class="main">
     
     <div id="content">
-      <h1 id="ExplicitProxyCaching">Explicit Proxy Caching</h1>
+      <div class="toc">
+<ul>
+<li><a href="#ExplicitProxyCaching">Explicit Proxy Caching</a><ul>
+<li><a href="#ConfiguringBrowsersManually">Configuring Browsers Manually</a></li>
+<li><a href="#UsingPACFile">Using a PAC File</a></li>
+<li><a href="#SamplePACFile">Sample PAC File</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<h1 id="ExplicitProxyCaching">Explicit Proxy Caching</h1>
 <p>If you want to use Traffic Server as an explicit proxy cache, you must configure 
 client software (i.e., browsers) to send requests directly to Traffic Server. </p>
-<h2 id="ExplicitProxyCachingforHTTP">Explicit Proxy Caching for HTTP</h2>
 <p>If you do not configure Traffic Server to use the transparency option (with 
 which client requests are intercepted en route to origin servers by a switch/router 
 and rerouted to the Traffic Server machine), then clients must configure their 
 web browsers to send HTTP requests to the Traffic Server proxy cache by configuring 
 their browsers to download proxy configuration instructions from a <a href="#UsingPACFile">PAC file</a> 
 (Proxy Auto-Configuration file).</p>
-<h3 id="ConfiguringBrowsersManually">Configuring Browsers Manually</h3>
+<h2 id="ConfiguringBrowsersManually">Configuring Browsers Manually</h2>
 <p>To manually configure a browser to send HTTP requests to Traffic Server, clients 
 must provide the following information: </p>
 <ul>
@@ -62,7 +71,7 @@ The procedures for manual configuration 
 to specific browser documentation for complete proxy configuration instructions. 
 You do not need to set any special configuration options on Traffic Server 
 if you want to accept requests from manually-configured browsers. </p>
-<h3 id="UsingPACFile">Using a PAC File</h3>
+<h2 id="UsingPACFile">Using a PAC File</h2>
 <p>A <strong>PAC file</strong> is a specialized JavaScript function definition that a browser 
 calls to determine how requests are handled. Clients must specify (in their 
 browser settings) the URL from which the PAC file is loaded. You can store 
@@ -76,7 +85,7 @@ perform the following configuration: </p
   <code>proxy.pac</code> file provided. The file is empty by default. A sample script is provided in <a href="#SamplePACFile">Sample PAC File</a>. </li>
 <li>Specify the port Traffic Server uses to serve the PAC file. The default port is <a href="../configuration-files/records.config#proxy.config.admin.autoconf_port">8083</a>.</li>
 </ul>
-<h4 id="SamplePACFile">Sample PAC File</h4>
+<h2 id="SamplePACFile">Sample PAC File</h2>
 <p>The following sample PAC file instructs browsers to connect directly to all 
 hosts without a fully-qualified domain name and to all hosts in the local domain. 
 All other requests go to the Traffic Server named <code>myproxy.company.com</code>.</p>