svn commit: r1129968 - in /trafficserver/site/branches/ats-cms/content/docs/trunk: STATUS admin/explicit-proxy-caching/index.en.mdtext

[ig...@apache.org]

Author: igalic
Date: Tue May 31 23:42:39 2011
New Revision: 1129968

URL: http://svn.apache.org/viewvc?rev=1129968&view=rev
Log:
Minor fixes to the explicit proxy caching chapter 

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS?rev=1129968&r1=1129967&r2=1129968&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS Tue May 31 23:42:39 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: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext?rev=1129968&r1=1129967&r2=1129968&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext Tue May 31 23:42:39 2011
@@ -16,13 +16,13 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
+[TOC]
+
 # Explicit Proxy Caching # {#ExplicitProxyCaching}
 
 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. 
 
-## Explicit Proxy Caching for HTTP ## {#ExplicitProxyCachingforHTTP}
-
 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 
@@ -30,7 +30,7 @@ web browsers to send HTTP requests to th
 their browsers to download proxy configuration instructions from a [PAC file](#UsingPACFile) 
 (Proxy Auto-Configuration file).
 
-### Configuring Browsers Manually  ### {#ConfiguringBrowsersManually}
+## Configuring Browsers Manually  ## {#ConfiguringBrowsersManually}
 
 To manually configure a browser to send HTTP requests to Traffic Server, clients 
 must provide the following information: 
@@ -45,7 +45,7 @@ to specific browser documentation for co
 You do not need to set any special configuration options on Traffic Server 
 if you want to accept requests from manually-configured browsers. 
 
-### Using a PAC File  ### {#UsingPACFile}
+## Using a PAC File  ## {#UsingPACFile}
 
 A **PAC file** is a specialized JavaScript function definition that a browser 
 calls to determine how requests are handled. Clients must specify (in their 
@@ -61,7 +61,7 @@ perform the following configuration: 
   `proxy.pac` file provided. The file is empty by default. A sample script is provided in [Sample PAC File](#SamplePACFile). 
 * Specify the port Traffic Server uses to serve the PAC file. The default port is [8083](../configuration-files/records.config#proxy.config.admin.autoconf_port).
 
-#### Sample PAC File  #### {#SamplePACFile}
+## Sample PAC File  ## {#SamplePACFile}
 
 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.