trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1164283 [1/3] - in /trafficserver/site/branches/ats-cms/content/docs/trunk: admin/cluster-howto/ admin/configuration-files/ admin/configuring-cache/ admin/faqs/ admin/working-log-files/ sdk/actions-guide/ sdk/adding-statistics/ sdk/continu...
Date Thu, 01 Sep 2011 21:34:30 GMT
Author: igalic
Date: Thu Sep  1 21:34:29 2011
New Revision: 1164283

URL: http://svn.apache.org/viewvc?rev=1164283&view=rev
Log:
s/\t/    /g

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/adding-statistics/coupled-statistics.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/writing-handler-functions.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/a-simple-plugin.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/plugin-registration-and-version-checking.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/implementing-the-handler-and-getting-a-handle-to-the-transaction.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/setting-a-transaction-hook.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/working-with-http-headers.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/blacklist-plugin/accessing-the-transaction-being-processed.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/blacklist-plugin/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/blacklist-plugin/setting-a-global-hook.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/blacklist-plugin/setting-up-a-transaction-hook.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/blacklist-plugin/working-with-http-header-functions.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/how-to-create-trafficserver-plugins/roadmap-for-creating-plugins.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/mime-fields-always-belong-to-an-associated-mime-header.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-headers/guide-to-trafficserver-http-header-system/release-marshal-buffer-handles.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-headers/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-headers/mime-headers.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-hooks-and-transactions/http-alternate-selection.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-hooks-and-transactions/http-sessions.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-hooks-and-transactions/http-transactions.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-transformation-plugin/append-transform-plugin.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-transformation-plugin/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/http-transformation-plugin/sample-null-transformation-plugin.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/io-guide/guide-to-cache-api/example.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/io-guide/guide-to-cache-api/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/io-guide/transformations.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/io-guide/vios.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/mutex-guide/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/new-protocol-plugins/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/plugin-configurations/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/remap-plugin/example-query-remap.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/sample-source-code/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/troubleshooting-tips/unable-to-debug-tags.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext Thu Sep  1 21:34:29 2011
@@ -93,13 +93,13 @@ individually. You may following these in
 1. setup the same cluster name, or proxy name, e.g. MyCluster:
 
                 ::::text
-		traffic_line -s proxy.config.proxy_name -v MyCluster
+        traffic_line -s proxy.config.proxy_name -v MyCluster
 
 2. enable cluster mode:
 
                 ::::text
-		traffic_line -s proxy.local.cluster.type -v 1
-		traffic_line -s proxy.config.cluster.ethernet_interface -v eth0
+        traffic_line -s proxy.local.cluster.type -v 1
+        traffic_line -s proxy.config.cluster.ethernet_interface -v eth0
  `eth0` should be replaced by your real interface, we recommends a 
  dedicated interface here. Refer to [`proxy.local.cluster.type`](../configuration-files/records.config#proxy.local.cluster.type)
  for a full description.

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/logs_xml.config.en.mdtext Thu Sep  1 21:34:29 2011
@@ -113,7 +113,7 @@ The following list shows the `LogFilter`
     -   `CASE_INSENSITIVE_MATCH` is similar to `MATCH`, except that it
     is case-**insensitive**.
     -   `CONTAIN` is true if the field contains the value (the value is
-   	   a substring of the field).
+          a substring of the field).
     -   `CASE_INSENSITIVE_CONTAIN` is a case-insensitive version of
     `CONTAIN`.
 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext Thu Sep  1 21:34:29 2011
@@ -211,18 +211,18 @@ In the following example, Traffic Server
 and you want to remove the image `remove_me.jpg` from cache:
 
       $ curl -X PURGE -v "http://example.com/remove_me.jpg"
-	 * About to connect() to example.com port 80 (#0)
-	 * Trying 192.0.32.11... connected 
-	 * Connected to example.com (192.0.32.11) port 80 (#0)
-
-	 > PURGE /remove_me.jpg HTTP/1.1
-	 > User-Agent: curl/7.19.7    
-	 > Host: example.com
-	 > Accept: */*
-	 >    
-	 < HTTP/1.1 200 Ok   
-	 < Date: Thu, 08 Jan 2010 20:32:07 GMT
-	 < Connection: keep-alive
+     * About to connect() to example.com port 80 (#0)
+     * Trying 192.0.32.11... connected 
+     * Connected to example.com (192.0.32.11) port 80 (#0)
+
+     > PURGE /remove_me.jpg HTTP/1.1
+     > User-Agent: curl/7.19.7    
+     > Host: example.com
+     > Accept: */*
+     >    
+     < HTTP/1.1 200 Ok   
+     < Date: Thu, 08 Jan 2010 20:32:07 GMT
+     < Connection: keep-alive
 
 The next time Traffic Server receives a request for the removed object, it 
 will contact the origin server to retrieve it (i.e., it has been purged from 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext Thu Sep  1 21:34:29 2011
@@ -15,66 +15,25 @@ Notice:    Licensed to the Apache Softwa
            KIND, either express or implied.  See the License for the
            specific language governing permissions and limitations
            under the License.
+Navigation: [*]()
 
 
-# Appendix G - FAQs and Troubleshooting Tips # {#AppendixG-FAQsTroubleshootingTips}
 
- This appendix contains the following sections:
+[TOC]()
 
-* [Frequently Asked Questions](#0_30488)
-* [Troubleshooting Tips](#0_96161)
+# FAQs # {#FAQs}
 
-## Frequently Asked Questions ## {#FrequentlyAskedQuestions}
+## How do you create a raw disk for the cache if all your disks have mounted file systems? ## {#raw-disk}
 
- FAQs
+Link to documentation
 
-  
-
-* [How do you create a raw disk for the cache if all your disks have mounted file systems?](#0_41244)
-* [How do disk I/O errors affect the cache and what does Traffic Server do when a cache disk fails?](#0_34163)
-* [If a client disconnects during the time that Traffic Server is downloading a large object, is any of the object saved in the cache?](#0_45613)
-* [Can Traffic Server cache Java applets, JavaScript programs, or other application files like VBScript?](#0_95054)
-* [How do you apply changes to the `logs_xml.config` file to all nodes in a cluster?](#0_37211)
-* [In Squid- and Netscape-format log files, what do the cache result codes mean?](#0_21826)
-* [What is recorded by the `cqtx` field in a custom log file?](#0_11719)
-* [Does Traffic Server refresh entries in its host database after a certain period of time if they haven't been used?](#0_42816)
-* [Can you improve the look of your custom response pages by using images, animated .gifs, and Java applets?](#0_12274)
-* [Can Traffic Server run in both forward proxy and reverse proxy mode at the same time?](#0_84580)
-* [How do I enable forward proxy mode?](#enable_forward_proxy)
-* [How do I interpret the Via: header code?](#interpret_via_header)
-* [Support for HTTP Expect: Header](#expect_header)
-
-###   _How do you create a raw disk for the cache if all your disks have mounted file systems?_ ### {#Howdoyoucreatearawdiskforcacheifallyourdiskshavemountedfilesystems?}
-
-####  To create a raw disk: #### {#createarawdisk}
-
-1.  As `root`, enter the following command at the prompt to examine which file systems are mounted on the disk you want to use for the Traffic Server cache:   
-`df -k`		  
-
-2.  In a text editor, open the 	
-				/etc/fstab file and comment out/delete the file system entries for the disk.
-3.  Save and close the `fstab` file.
-4.  Enter the following command for each file system you want to unmount:  
-`umount _file_system_`
-		
- where `_ file_system_` is the file system you want to unmount. 
-5.  Install Traffic Server. When the installation script prompts you for a cache disk, select the raw disk you just created.
-
-_
 
-### How do disk I/O errors affect the cache and what does Traffic Server do when a cache disk fails? ### {#HowdodiskI/OerrorsaffectcachewhatdoesTSdowhenacachediskfails?}
+## How do disk I/O errors affect the cache and what does Traffic Server do when a cache disk fails? ## {#disk-io-fail}
 
-_
+If a disk drive fails five successive I/O operations, then Traffic Server considers the drive inaccessible
+and removes the entire disk from the cache. Normal cache operations continue for all other Traffic Server disk drives.
 
-If a disk drive fails five successive I/O operations, then Traffic Server considers the drive inaccessible and removes the entire disk from the cache. Normal cache operations continue for all other Traffic Server disk drives._
-_
-
-_
-__
-
-### If a client disconnects during the time that Traffic Server is downloading a large object, is any of the object saved in the cache? ### {#IfaclientdisconnectsduringtimethatTSisdownloadingalargeobject,isanyofobjectsavedincache?}
-
-_
+#### If a client disconnects during the time that Traffic Server is downloading a large object, is any of the object saved in the cache? #### {#client-disco-lo}
 
 When a client disconnects during an HTTP operation, Traffic Server continues 
 to download the object from the origin server for up to 10 seconds. If the 
@@ -84,310 +43,101 @@ origin server download does _not_ comple
 then Traffic Server disconnects from the origin server and deletes the object 
 from cache. Traffic Server does not store partial documents in the cache.
 
-_
+#### Can Traffic Server cache Java applets, JavaScript programs, or other application files like VBScript? #### {#cache-java}
 
-### Can Traffic Server cache Java applets, JavaScript programs, or other application files like VBScript? ### {#CanTScacheJavaapplets,JavaScriptprograms,otherapplicationfileslikeVBScript?}
+Yes, Traffic Server can store and serve Java applets, JavaScript programs, VBScripts, and other executable objects
+from its cache according to the freshness and cacheability rules for HTTP objects. Traffic Server does not execute
+the applets, scripts, or programs, however - these objects run only when the client system (ie, the one that sent the request) loads them.
 
-_
 
-Yes, Traffic Server can store and serve Java applets, JavaScript programs, VBScripts, and other executable objects from its cache according to the freshness and cacheability rules for HTTP objects. Traffic Server does not execute the applets, scripts, or programs, however - these objects run only when the client system (ie, the one that sent the request) loads them._
-__
-_
+#### How do you apply changes to the `logs_xml.config` file to all nodes in a cluster? #### {#apply-logxml}
 
-_
-
-### How do you apply changes to the `logs_xml.config` file to all nodes in a cluster? ### {#Howdoyouapplychanges`logsxml.config`fileallnodesinacluster?}
+Link to documentation
 
-_
-
- After you modify the 	
-	  logs_xml.config file on one Traffic Server node, enter the following command from the Traffic Server 	
-	  bin directory:  
-` traffic_line -x`
-
-  
-  
- Traffic Server applies the changes to all nodes in the cluster. The changes take effect immediately.__
-
-_
-
-### In Squid- and Netscape-format log files, what do the cache result codes mean? ### {#InSquid-Netscape-formatlogfiles,whatdocacheresultcodesmean?}
-
-_
+#### In Squid- and Netscape-format log files, what do the cache result codes mean? #### {#squid-netscape-result-codes}
 
 The following table describes the cache result codes in Squid and Netscape 
 log files.
 
-_
-**
-  
-
- Cache Result Code
-
-  ** **
-  
-
- Description
-
-  ** 
-
-  
-
-	
-	    TCP_HIT 
-
-  
-:   
-      
-    
-     A valid copy of the requested object was in the cache and Traffic Server sent 
+`TCP_HIT`
+:   A valid copy of the requested object was in the cache and Traffic Server sent 
     the object to the client. 
     
-    
-      
-
-  
-
-	
-	    TCP_MISS
-
-  
-:   
-      
-    
-     The requested object was not in cache, so Traffic Server retrieved the object 
+`TCP_MISS`
+:   The requested object was not in cache, so Traffic Server retrieved the object 
     from the origin server (or a parent proxy) and sent it to the client.
-    
-    
-      
-
-  
-
-	
-	    TCP_REFRESH_HIT 
-
-  
-:   
-      
-    
-     The object was in the cache, but it was stale. Traffic Server made an 	
-    	      if-modified-since request to the origin server and the origin server sent a 	
-    	      304 not-modified response. Traffic Server sent the cached object to the client.
-    
-    
-      
-
-  
-
-	
-	    TCP_REF_FAIL_HIT
-
-  
-:   
-      
-    
-     The object was in the cache but was stale. Traffic Server made an 	
-    	      if-modified-since request to the origin server but the server did not respond_._ Traffic Server sent the cached object to the client.
-    
-    
-      
-
-  
-
-	
-	    TCP_REFRESH_MISS
-
-  
-:   
-      
-    
-     The object was in the cache but was stale. Traffic Server made an 	
-    	      if-modified-since request to the origin server and the server returned a new object_._ Traffic Server served the new object to the client.
-    
-    
-      
 
-  
-
-	
-	    TCP_CLIENT_REFRESH
+`TCP_REFRESH_HIT `
+:   The object was in the cache, but it was stale. Traffic Server made an     
+    `if-modified-since` request to the origin server and the origin server sent a     
+    `304` not-modified response. Traffic Server sent the cached object to the client.
+ 
+`TCP_REF_FAIL_HIT`
+:   The object was in the cache but was stale. Traffic Server made an     
+    `if-modified-since` request to the origin server but the server did not respond.
+    Traffic Server sent the cached object to the client.
+
+`TCP_REFRESH_MISS`
+:   The object was in the cache but was stale. Traffic Server made an     
+    `if-modified-since` request to the origin server and the server returned a new object.
+    Traffic Server served the new object to the client.
 
-  
-:   
-      
-    
-     The client issued a request with a `no-cache` header. Traffic Server obtained 
+`TCP_CLIENT_REFRESH`
+:   The client issued a request with a `no-cache` header. Traffic Server obtained 
     the requested object from the origin server and sent a copy to the client. 
     Traffic Server deleted the previous copy of the object from cache.
-    
-    
-      
-
-  
-
-	
-	    TCP_IMS_HIT 
 
-  
-:   
-      
-    
-     The client issued an 	
-    	      if-modified-since request and the object was in cache & fresher than the IMS date, **or** an 	
-    	      if-modified-since request to the origin server revealed the cached object was fresh. Traffic Server served the cached object to the client.
-    
-    
-      
-
-  
-
-	
-	    TCP_IMS_MISS
-
-  
-:   
-      
+`TCP_IMS_HIT`
+:   The client issued an     
+    `if-modified-since` request and the object was in cache & fresher than the IMS date, **or** an     
+    `if-modified-since` request to the origin server revealed the cached object was fresh.
+    Traffic Server served the cached object to the client.
+    
+`TCP_IMS_MISS`
+:   The client issued an     
+    `if-modified-since request`, and the object was either not in cache or was stale in cache. Traffic Server sent an     
+    `if-modified-since request` to the origin server and received the new object. Traffic Server sent the updated object to the client.
     
-     The client issued an 	
-    	      if-modified-since request, and the object was either not in cache or was stale in cache. Traffic Server sent an 	
-    	      if-modified-since request to the origin server and received the new object. Traffic Server sent the updated object to the client.
-    
-    
-      
-
-  
-
-	
-	    TCP_SWAPFAIL 
-
-  
-:   
-      
-    
-     The object was in the cache but could not be accessed. The client did not 
+`TCP_SWAPFAIL`
+:   The object was in the cache but could not be accessed. The client did not 
     receive the object.
     
-    
-      
-
-  
-
-	
-	    ERR_CLIENT_ABORT 
-
-  
-:   
-      
-    
-     The client disconnected before the complete object was sent.
-    
-    
-      
-
-  
-
-	
-	    ERR_CONNECT_FAIL
-
-  
-:   
-      
-    
-     Traffic Server could not reach the origin server.
-    
-    
-      
-
-  
+`ERR_CLIENT_ABORT`
+:   The client disconnected before the complete object was sent.
 
-	
-	    ERR_DNS_FAIL
+`ERR_CONNECT_FAIL`
+:   Traffic Server could not reach the origin server.
 
-  
-:   
-      
-    
-     The Domain Name Server (DNS) could not resolve the origin server name, or 
+`ERR_DNS_FAIL`
+:   The Domain Name Server (DNS) could not resolve the origin server name, or 
     no DNS could be reached.
-    
-    
-      
-
-  
-
-	
-	    ERR_INVALID_REQ 
 
-  
-:   
-      
-    
-     The client HTTP request was invalid. (Traffic Server forwards requests with 
+`ERR_INVALID_REQ`
+:   The client HTTP request was invalid. (Traffic Server forwards requests with 
     unknown methods to the origin server.) 
-    
-    
-      
-
-  
-
-	
-	    ERR_READ_TIMEOUT
 
-  
-:   
-      
-    
-     The origin server did not respond to Traffic Server's request within the timeout 
+`ERR_READ_TIMEOUT`
+:   The origin server did not respond to Traffic Server's request within the timeout 
     interval.
-    
-    
-      
-
-  
-
-	
-	    ERR_PROXY_DENIED
-
-  
-:   
-      
-    
-     Client service was denied.
-    
-    
-      
-
-  
-
-	
-	    ERR_UNKNOWN
-
-  
-:   
-      
-    
-     The client connected, but subsequently disconnected without sending a request. 
-    
-    
-    
-      
 
-### What is recorded by the `cqtx` field in a custom log file? ### {#Whatisrecordedby`cqtx`fieldinacustomlogfile?}
+`ERR_PROXY_DENIED`
+:   Client service was denied.
 
-_
 
-In **forward proxy mode**, the 	
-	  cqtx field records the complete client request in the log file (for example, 	
-	  GET http://www.company.com HTTP/1.0 ).   
- In **reverse proxy mode**, the 	
-	  cqtx field records the hostname or IP address of the origin server because Traffic Server first remaps the request as per map rules in the 	
-	  remap.config file.
+`ERR_UNKNOWN`
+:   The client connected, but subsequently disconnected without sending a request. 
 
-_
+#### What is recorded by the `cqtx` field in a custom log file? #### {#whatis-cqtx}
 
-### Does Traffic Server refresh entries in its host database after a certain period of time if they have not been used? ### {#DoesTSrefreshentriesinitshostdatabaseafteracertainperiodoftimeiftheyhavenotbeenused?}
+* In **forward proxy mode**, the     
+      cqtx field records the complete client request in the log file (for example,     
+      GET http://www.company.com HTTP/1.0 ).
+* In **reverse proxy mode**, the     
+      cqtx field records the hostname or IP address of the origin server because
+      Traffic Server first remaps the request as per map rules in the     
+      [remap.config](../configuration-files/remap.config) file.
 
-_
+#### Does Traffic Server refresh entries in its host database after a certain period of time if they have not been used? #### {#ts-refresh-hostdb}
 
 By default, the Traffic Server host database observes the time-to-live (`ttl`) 
 values set by name servers. You can reconfigure Traffic Server to ignore the 
@@ -398,91 +148,101 @@ use either the lower or the higher value
 
 #### To adjust the host database settings: #### {#adjusthostdatabasesettings}
 
-1. In a text editor, open the 	
-				records.config file located in the Traffic Server 	
-				config directory. 
-2.  Set the value of the variable 	
-				proxy.config.hostdb.ttl_mode to:
-
-* 		
-				  0 to obey `ttl` values set by the name servers.
-* 		
-				  1 to ignore `ttl` values set by name servers and instead use the value set by the Traffic Server configuration variable 	
-				proxy.config.hostdb.timeout (make sure you set this variable to a value appropriate for your needs).
-* 		
-				2 to use the lower of the two values (i.e., either the value set by the name server or the one set by Traffic Server).
-* 		
-				3 to use the higher of the two values.
-
- Save and close the 	
-	    records.config file.   
- From the Traffic Server 	
-	      bin directory, run the command 	
-	      traffic_line -x  to apply the configuration changes. 
-
-_
-
-### Can you improve the look of your custom response pages by using images, animated .gifs, and Java applets? ### {#Canyouimprovelookofyourcustomresponsepagesbyusingimages,animated.gifs,Javaapplets?}
+<!-- XXX: Put this into the records.config docs -->
+1. In a text editor, open the     
+                records.config file located in the Traffic Server     
+                config directory. 
+2.  Set the value of the variable     
+                proxy.config.hostdb.ttl_mode to:
+
+*         
+                  0 to obey `ttl` values set by the name servers.
+*         
+                  1 to ignore `ttl` values set by name servers and instead use the value set by the Traffic Server configuration variable     
+                proxy.config.hostdb.timeout (make sure you set this variable to a value appropriate for your needs).
+*         
+                2 to use the lower of the two values (i.e., either the value set by the name server or the one set by Traffic Server).
+*         
+                3 to use the higher of the two values.
+
+ Save and close the     
+        records.config file.   
+ From the Traffic Server     
+          bin directory, run the command     
+          traffic_line -x  to apply the configuration changes. 
+
+#### Can you improve the look of your custom response pages by using images, animated .gifs, and Java applets? #### {#style-custom-pages}
+
+<!-- XXX: This sounds wrong. -->
+No, because Traffic Server can only respond to clients with a single text or HTML document.
+As a workaround, however, you can provide references on your custom response pages to images,
+animated .gifs, Java applets, or objects other than text which are located on a web server.
+Add links in the body_factory template files in the same way you would for any image in an HTML document (i.e., with the full URL in the `SRC` attribute).
+
+#### Can Traffic Server run in forward proxy and reverse proxy modes at the same time? #### {#run-forward-reverse-same-time}
+
+Yes. When you enable reverse proxy mode, Traffic Server remaps incoming requests according to the map rules in the     
+[`remap.config`](../configuration-files/remap.config) file. All other requests that do not match a map rule are simply served in forward proxy mode.
+
+If you want to run in reverse proxy only mode (wherein Traffic Server does _not_ serve requests that fail to match a map rule), then you must set the configuration variable     
+proxy.config.url_remap.remap_required to 1 in the [`records.config`](../configuration-files/records.config) file. 
+
+#### How do I enable forward proxy mode #### {#forward-proxy}
+
+<!--- TODO: This should be it's own short document -->
+
+Forward proxy mode is not enabled out of the box for security reasons.
+When enabling any proxy on the internet, you want to make sure you observe
+pertinent security restrictions. Having an open proxy available to internet
+users is a bad thing. If you understand this and are sure you know what you are doing,
+in [`records.config`](../configuration-files/records.config):
+
+    ::::text
+    # Set this variable to 1 if you want Traffic Server to serve 
+    # requests only from origin servers listed in the mapping rules
+    # of the remap.config file. If a request does not match, then 
+    # the browser will receive an error.
+    CONFIG proxy.config.url_remap.remap_required INT 0
 
-_
-
-No, because Traffic Server can only respond to clients with a single text or HTML document. As a workaround, however, you can provide references on your custom response pages to images, animated .gifs, Java applets, or objects other than text which are located on a web server. Add links in the 	
-	  body_factory template files in the same way you would for any image in an HTML document (i.e., with the full URL in the `SRC` attribute).
-
-_
-
-### Can Traffic Server run in forward proxy and reverse proxy modes at the same time? ### {#CanTSruninforwardproxyreverseproxymodesatsametime?}
-
-_
 
- Yes. When you enable reverse proxy mode, Traffic Server remaps incoming requests according to the map rules in the 	
-	  remap.config file. All other requests that do not match a map rule are simply served in forward proxy mode.   
- If you want to run in reverse proxy only mode (wherein Traffic Server does _not_ serve requests that fail to match a map rule), then you must set the configuration variable 	
-	  proxy.config.url_remap.remap_required to 1 in the `records.config` file. 
-
-### _How do I enable forward proxy mode_ ### {#HowdoIenableforwardproxymode}
-
-Forward proxy mode is not enabled out of the box for security reasons. When enabling any proxy on the internet, you want to make sure you observe pertinent security restrictions. Having an open proxy available to internet users is a bad thing. If you understand this and are sure you know what you are doing, in `records.config`:  
-	
-	    # Set this variable to 1 if you want Traffic Server to serve 
-	    # requests only from origin servers listed in the mapping rules
-	    # of the remap.config file. If a request does not match, then 
-	    # the browser will receive an error.
-	    CONFIG proxy.config.url_remap.remap_required INT 0
-
-### _How do I interpret the Via: header code?_ ### {#HowdoIinterpretViaheadercode?}
+#### How do I interpret the Via: header code? #### {#interpret-via}
 
+<!--- TODO: put this in records.config? -->
 The Via header is an optional HTTP header added by Traffic Server and other 
 HTTP proxies. If a request goes through multiple proxies, each one appends 
 its Via header content to the end of the existing Via header. Via header content 
 is for general information and diagnostic use only and should not be used as 
 a programmatic interface to Traffic Server. 
 
- The form of the Via header is 
+The form of the Via header is 
 
- Via: _<protocol> <proxyname>_ (_<product/version> [_<via-codes>_])
+Via: _`<protocol> <proxyname>` (<product/version> [<via-codes>])_
 
- _<protocol>_  the scheme and version of the HTTP request   
+ _<protocol>_  the scheme and version of the HTTP request
 
- _<proxyname>_  the configured name of the proxy server   
+ _<proxyname>_  the configured name of the proxy server
 
- _<product/version>_  the Inktomi Network Products product name and version   
+ _<product/version>_  the Inktomi Network Products product name and version
 
  _<via-codes>_  a string of alphabetic codes presenting status information about the proxy 
 handling of the HTTP request 
 
  For example:
 
-<p>	
-	Via: HTTP/1.0 storm (Traffic-Server/4.0.0   [cMs f ]) 
-	      [u lH o  f  pS eN]     cache hit
-	      [u lM oS fF pS eN]     cache miss
-	      [uN l oS f  pS eN]     no-cache origin server fetch
-	 The short status code shows the cache-lookup, server-info and cache-fill information as listed in the full status code description below. The long status code list provided in older, commercial versions of Traffic Server can be restored by setting the verbose_via_str config variable. 
+    Via: HTTP/1.0 storm (Traffic-Server/4.0.0   [cMs f ]) 
+          [u lH o  f  pS eN]     cache hit
+          [u lM oS fF pS eN]     cache miss
+          [uN l oS f  pS eN]     no-cache origin server fetch
+The short status code shows the cache-lookup, server-info and cache-fill information as listed
+in the full status code description below. The long status code list provided in older,
+commercial versions of Traffic Server can be restored by setting the
+`verbose_via_str` config variable. 
+
+The character strings in the via-code show `[<request results>:<proxy op>]` where _<request results>_
+represents status information about the results of the client request and _<proxy op>_ represent some
+information about the proxy operations performed during request processing. The full via-code status format is 
 
- The character strings in the via-code show [_<request results>_:_<proxy op>_] where _<request results>_ represents status information about the results of the client request and _<proxy op>_ represent some information about the proxy operations performed during request processing. The full via-code status format is 
-
-[u_<client-info>_ c_<cache-lookup>_ s_<server-info>_
+_`[u<client-info> c<cache-lookup> s<server-info>`_
 
 f_<cache-fill>_ p_<proxy-info>_ e_<error-codes>_
 
@@ -682,50 +442,28 @@ Traffic Server currently does not handle
 
  Note that clients such as cURL automatically send Expect: for POST requests with large POST bodies, with a 1 second timeout if a 100 Continue response is not received. To avoid the timeout when using cURL as a client to Traffic Server, you can turn off the Expect: header as follows:
 
- command line: 	
-	curl -H"Expect:" http://www.example.com/
-	
-
- C (libcurl): 	
-	struct curl_slist *header_list=NULL;
-	header_list = curl_slist_append(header_list, "Expect:"); 
-	curl_easy_setopt(my_curlp, CURLOPT_HTTPHEADER, header_list); 
-	
-
- php: 	
-	curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); 
-	
-
-   
-   
-
-## Troubleshooting Tips ## {#TroubleshootingTips}
-
- Troubleshooting Tip
-
-      
-
-* [The throughput statistic is inaccurate ](#0_22364)
-* [You are unable to execute Traffic Line commands](#0_48340)
-* [You observe inconsistent behavior when one node obtains an object from another node in the cluster](#0_42829)
-* [Web browsers display an error document with a "data missing" message](#0_29076)
-* [Traffic Server does not resolve any websites](#0_45366)
-* ["Maximum document size exceeded" message in the system log file](#0_13841)
-* ["DrainIncomingChannel" message in the system log file](#0_76993)
-* ["No cop file" message in the system log file](#0_73746)
-* [Warning in system log file when manually editing `vaddrs.config`](#0_67754)
-* [Nontransparent requests fail after enabling `always_query_destination`](#0_57248)
-* [Traffic Server is running but no log files are created](#0_47006)
-* [Traffic Server shows an error indicating too many network connections](#0_82182)
-* [Low memory symptoms](#0_93012)
-* [Connection timeouts with the origin server](#0_56862)
-* [IBM Web servers do not work with Traffic Server](#0_13091)
+command line:     
 
-_
+    curl -H"Expect:" http://www.example.com/
+    
 
-### The throughput statistic is inaccurate ### {#throughputstatisticisinaccurate}
+C (libcurl):     
+
+    struct curl_slist *header_list=NULL;
+    header_list = curl_slist_append(header_list, "Expect:"); 
+    curl_easy_setopt(my_curlp, CURLOPT_HTTPHEADER, header_list); 
+    
+
+php:     
+
+    curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); 
+    
 
-_
+
+# Troubleshooting Tips # {#trouble-shooting}
+
+
+### The throughput statistic is inaccurate ### {#throughputstatisticisinaccurate}
 
 Traffic Server updates the throughput statistic after it has transferred an 
 entire object. For larger files, the byte count increases sharply at the end 
@@ -734,8 +472,6 @@ last 10-second interval, although it can
 object. This inaccuracy is more noticeable with a light load. A heavier load 
 yields a more accurate statistic.
 
-_
-
 ### You are unable to execute Traffic Line commands ### {#YouareunableexecuteTrafficLinecommands}
 
 _
@@ -769,9 +505,9 @@ on all nodes in your cluster. Minor time
 but differences of more than a few minutes can affect Traffic Server operation. 
  
 
- You should run a clock synchronization daemon such as 	
-	  xntpd. To obtain the latest version of 	
-	  xntpd, go to `http://www.eecis.udel.edu/~ntp/`  
+ You should run a clock synchronization daemon such as     
+      xntpd. To obtain the latest version of     
+      xntpd, go to `http://www.eecis.udel.edu/~ntp/`  
 
 _
 
@@ -779,10 +515,10 @@ _
 
 _ A message similar to the following might display in web browsers: 
 
-> 	
-> 	  Data Missing    
-> 	
-> 	This document resulted from a POST operation and has expired from the cache. You can repost the form data to recreate the document by pressing the Reload button.
+>     
+>       Data Missing    
+>     
+>     This document resulted from a POST operation and has expired from the cache. You can repost the form data to recreate the document by pressing the Reload button.
 
  This is a Web browser issue and not a problem specific to (or caused by) Traffic 
 Server. Because Web browsers maintain a separate local cache in memory and/or 
@@ -803,20 +539,20 @@ the following message: 
 > 
 >   
 > 
->     	
-> 	    The document contains no data; Try again later, or contact the server's Administrator...
+>         
+>         The document contains no data; Try again later, or contact the server's Administrator...
 >   
 > 
 
  Make sure the system is configured correctly and that Traffic Server can read 
 the name resolution file: 
 
-* Check if the server can resolve DNS lookups by issuing the 	
-				nslookup command (for example, `nslookup www.myhost.com`).
+* Check if the server can resolve DNS lookups by issuing the     
+                nslookup command (for example, `nslookup www.myhost.com`).
 *  Check if the `/etc/resolv.conf` file contains valid IP addresses for your DNS servers.
 *  On some systems, if the `/etc/resolv.conf` file is unreadable or has no name server entry, then the operating system uses `localhost` as a name server. Traffic Server, however, does not use this convention. If you want to use `localhost` as a name server, then you must add a name server entry for `127.0.0.1` or `0.0.0.0` in the `/etc/resolv.conf` file. 
-*  Check that the Traffic Server user account has permission to read the 	
-		  /etc/resolv.conf file. If it does not, then change the file permissions to `rw-r--r--` (`644`)
+*  Check that the Traffic Server user account has permission to read the     
+          /etc/resolv.conf file. If it does not, then change the file permissions to `rw-r--r--` (`644`)
 
 _
 
@@ -829,14 +565,14 @@ The following message appears in the sys
 > 
 >   
 > 
->     	
-> 	    WARNING: Maximum document size exceeded
+>         
+>         WARNING: Maximum document size exceeded
 >   
 > 
 
- A requested object was larger than the maximum size allowed in the Traffic Server cache, so Traffic Server provided proxy service for the oversized object but did not cache it. To set the object size limit for the cache, modify the 	
-	  proxy.config.cache.limits.http.max_doc_size variable in the 	
-	  records.config file. If you do not want to limit the size of objects in the cache, then set the document size to` **0**`(zero).
+ A requested object was larger than the maximum size allowed in the Traffic Server cache, so Traffic Server provided proxy service for the oversized object but did not cache it. To set the object size limit for the cache, modify the     
+      proxy.config.cache.limits.http.max_doc_size variable in the     
+      records.config file. If you do not want to limit the size of objects in the cache, then set the document size to` **0**`(zero).
 
 _
 
@@ -899,12 +635,12 @@ The following message appears repeatedly
 >   
 > 
 
- The file `config/internal/no_cop` acts as an administrative control that instructs the `traffic_cop` process to exit immediately without starting `traffic_manager` or performing any health checks. The `no_cop` file prevents Traffic Server from starting automatically when it has been stopped with the `stop_traffic_server` command. Without this static control, Traffic Server would restart automatically upon system reboot. The `no_cop` control keeps Traffic Server off until it is explicitly restarted with the 	
-	start_traffic_server command.
+ The file `config/internal/no_cop` acts as an administrative control that instructs the `traffic_cop` process to exit immediately without starting `traffic_manager` or performing any health checks. The `no_cop` file prevents Traffic Server from starting automatically when it has been stopped with the `stop_traffic_server` command. Without this static control, Traffic Server would restart automatically upon system reboot. The `no_cop` control keeps Traffic Server off until it is explicitly restarted with the     
+    start_traffic_server command.
 
- The Traffic Server installation script also creates a 	
-	  no_cop file so that Traffic Server does not start automatically. After you have completed installation/configuration and have rebooted the operating system, use the 	
-	  start_traffic_server command to start Traffic Server.
+ The Traffic Server installation script also creates a     
+      no_cop file so that Traffic Server does not start automatically. After you have completed installation/configuration and have rebooted the operating system, use the     
+      start_traffic_server command to start Traffic Server.
 
 _
 
@@ -912,14 +648,14 @@ _
 
 _
 
- If you manually edit the 	
-	  vaddrs.config file as a non-root user, then Traffic Server issues a warning message in the system log file similar to the following:
+ If you manually edit the     
+      vaddrs.config file as a non-root user, then Traffic Server issues a warning message in the system log file similar to the following:
 
 > 
 >   
 > 
->     	
-> 	    WARNING: interface is ignored: Operation not permitted
+>         
+>         WARNING: interface is ignored: Operation not permitted
 >   
 > 
 
@@ -932,9 +668,9 @@ _
 
 _
 
- The variable 	
-	  proxy.config.arm.always_query_dest  in the 	
-	  records.config file configures Traffic Server in transparent mode to ignore host headers and always ask for the IP address of the origin server. When you enable this variable, Traffic Server obtains the origin server IP address from the existing NAT map list rather than trying to resolve the destination hostname with a DNS lookup. As a result, logged URLs contain only IP addresses and no hostnames. However, explicit requests (nontransparent requests, including requests on port 80) fail, as there is no matching map in the NAT list. The `always_query_destination` option works only on the primary proxy port.
+ The variable     
+      proxy.config.arm.always_query_dest  in the     
+      records.config file configures Traffic Server in transparent mode to ignore host headers and always ask for the IP address of the origin server. When you enable this variable, Traffic Server obtains the origin server IP address from the existing NAT map list rather than trying to resolve the destination hostname with a DNS lookup. As a result, logged URLs contain only IP addresses and no hostnames. However, explicit requests (nontransparent requests, including requests on port 80) fail, as there is no matching map in the NAT list. The `always_query_destination` option works only on the primary proxy port.
 
 _
 
@@ -946,18 +682,18 @@ Traffic Server only writes event log fil
 If Traffic Server is idle, then it's possible/probable that no log files exist. 
 In addition: 
 
-Make sure you're looking in the correct directory. By default, Traffic Server creates log files in the 	
-	  logs directory. 
-Check the location of log files by checking the value of the variable 	
-	  proxy.config.log.logfile_dir  in the 	
-	  records.config file. Check that the log directory has read/write permissions for the Traffic Server user account. If the log directory does not have the correct permissions, then the 	
-	  traffic_server process is unable to open or create log files.
-Check that logging is enabled by checking the value of the 	
-	  proxy.config.log.logging_enabled variable in the 	
-	  records.config file. 
-Check that a log format is enabled. In the 	
-	  records.config file, select the standard or custom format by editing variables in the 	
-	  Logging Config section.
+Make sure you're looking in the correct directory. By default, Traffic Server creates log files in the     
+      logs directory. 
+Check the location of log files by checking the value of the variable     
+      proxy.config.log.logfile_dir  in the     
+      records.config file. Check that the log directory has read/write permissions for the Traffic Server user account. If the log directory does not have the correct permissions, then the     
+      traffic_server process is unable to open or create log files.
+Check that logging is enabled by checking the value of the     
+      proxy.config.log.logging_enabled variable in the     
+      records.config file. 
+Check that a log format is enabled. In the     
+      records.config file, select the standard or custom format by editing variables in the     
+      Logging Config section.
 _
 
 ### Traffic Server shows an error indicating too many network connections ### {#TSshowsanerrorindicatingtoomanynetworkconnections}
@@ -977,8 +713,8 @@ until the connection count falls below t
 *  If there is a **connection spike** (e.g., if thousands of client requests all reach Traffic Server at the same time). Such events are typically transient and require no corrective action.
 *  If there is a **service overload** (e.g., if client requests continuously arrive faster than Traffic Server can service them). Service overloads often indicate network problems between Traffic Server and origin servers. Conversely, it may indicate that Traffic Server needs more memory, CPU, cache disks, or other resources to handle the client load.
 
- If necessary, you can reset the maximum number of connections supported by Traffic Server by editing the value of the `_proxy.config.net.connections_throttle _` configuration variable in the 	
-	records.config file. Do not increase the connection throttle limit unless the system has adequate memory to handle the client connections required. A system with limited RAM might need a throttle limit lower than the default value. Do not set this variable below the minimum value of 100.
+ If necessary, you can reset the maximum number of connections supported by Traffic Server by editing the value of the `_proxy.config.net.connections_throttle _` configuration variable in the     
+    records.config file. Do not increase the connection throttle limit unless the system has adequate memory to handle the client connections required. A system with limited RAM might need a throttle limit lower than the default value. Do not set this variable below the minimum value of 100.
 
 _
 
@@ -1020,9 +756,9 @@ _
 
 _
 
-Certain origin servers take longer than 30 seconds to post HTTP requests, which results in connection timeouts with Traffic Server. To prevent such connection timeouts, you must change the value of the configuration variable 	
-	  proxy.config.http.connect_attempts_timeout  in the	
-	  records.config file to 60 seconds or more.
+Certain origin servers take longer than 30 seconds to post HTTP requests, which results in connection timeouts with Traffic Server. To prevent such connection timeouts, you must change the value of the configuration variable     
+      proxy.config.http.connect_attempts_timeout  in the    
+      records.config file to 60 seconds or more.
 
 _
 
@@ -1039,27 +775,27 @@ variable. 
 1.  In a text editor, open the `records.config` file located in the Traffic Server `config` directory.
 2.  Edit the following configuration variable:   
 **
-				  
+                  
  Variable
-				** **
-				  
+                ** **
+                  
  Description
-				** 
-				  
+                ** 
+                  
 _
-				  `proxy.config.ssl.TLSv1`_
-				
+                  `proxy.config.ssl.TLSv1`_
+                
 :   
-						  
-		
-		 Set this variable to `**0**` (zero).
-		
-		
-						
+                          
+        
+         Set this variable to `**0**` (zero).
+        
+        
+                        
 
-3.  Save and close the 	
-				records.config file.
+3.  Save and close the     
+                records.config file.
 4.  Navigate to the Traffic Server `bin` directory. 
-5.  Run the command 	
-				traffic_line -x  to apply the configuration changes._  _  
+5.  Run the command     
+                traffic_line -x  to apply the configuration changes._  _  
 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/index.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/index.en.mdtext Thu Sep  1 21:34:29 2011
@@ -1,3 +1,4 @@
+Title: Working with Log Files
 Notice:    Licensed to the Apache Software Foundation (ASF) under one
            or more contributor license agreements.  See the NOTICE file
            distributed with this work for additional information
@@ -22,16 +23,7 @@ it receives and every error it detects.
 
 This chapter discusses the following topics: 
 
-* [Understanding Traffic Server Log Files](#UnderstandingTSLogFiles)
-* [Understanding Event Log Files](#UnderstandingEventLogFiles)
-* [Managing Event Log Files](#ManagingEventLogFiles)
-* [Choosing Event Log File Formats](#ChoosingEventLogFileFormats)
-* [Rolling Event Log Files](#RollingEventLogFiles)
-* [Splitting Event Log Files](#SplittingEventLogFiles)
-* [Collating Event Log Files](#CollatingEventLogFiles)
-* [Viewing Logging Statistics](#ViewingLoggingStatistics)
-* [Viewing Log Files](#ViewingLogFiles)
-* [Example Event Log File Entries](#ExampleEventLogFileEntries)
+[TOC]()
 
 ## Understanding Traffic Server Log Files ## {#UnderstandingTSLogFiles}
 
@@ -47,21 +39,21 @@ types of log files: 
 * **System log files** record system information, including messages about the state of
   Traffic Server and errors/warnings it produces. This kind of information might include a
   note that event log files were rolled, a warning that cluster communication timed out, or
-  an error indicating that Traffic Server was restarted.   
+  an error indicating that Traffic Server was restarted. 
 
       All system information messages are logged with the system-wide logging facility **`syslog`**
   under the daemon facility. The `syslog.conf` configuration file (stored in the `/etc` directory)
-  specifies where these messages are logged. A typical location is `/var/log/messages` (Linux).   
+  specifies where these messages are logged. A typical location is `/var/log/messages` (Linux).
 
       The `syslog` process works on a system-wide basis, so it serves as the single repository for
-  messages from all Traffic Server processes (including `traffic_server`, `traffic_manager`, and `traffic_cop`).   
-  
+  messages from all Traffic Server processes (including `traffic_server`, `traffic_manager`, and `traffic_cop`).
+
       System information logs observe a static format. Each log entry in the log contains
   information about the date and time the error was logged, the hostname of the Traffic
-  Server that reported the error, and a description of the error or warning.   
+  Server that reported the error, and a description of the error or warning. 
 
       Refer to [Traffic Server Error Messages](../traffic-server-error-messages) for a list of the messages
-      logged by Traffic Server. 
+   logged by Traffic Server. 
 
 By default, Traffic Server creates both error and event log files and records 
 system information in system log files. You can disable event logging and/or 
@@ -100,7 +92,7 @@ and discuss how to:
       You can choose which standard log file formats you want to use for traffic analysis,
   such as Squid or Netscape. Alternatively, you can use the Traffic Server custom format,
   which is XML-based and enables you to institute more control over the type of information
-  recorded in log files. Refer to [Choosing Event Log File Formats](#ChoosingEventLogFileFormats).   
+  recorded in log files. Refer to [Choosing Event Log File Formats](#ChoosingEventLogFileFormats).
 
 * **Roll event log files automatically**
 
@@ -188,8 +180,11 @@ Traffic Server supports the following lo
 * Standard formats, such as Squid or Netscape; refer to [Using Standard Formats](#UsingStandardFormats). 
 * The Traffic Server custom format; refer to [Using the Custom Format](#UsingCustomFormat). 
 
-In addition to the standard and custom log file format, you can choose whether to save log files in binary or ASCII; refer to [Choosing Binary or ASCII](#ChoosingBinaryASCII).   
- Event log files consume substantial disk space. Creating log entries in multiple formats at the same time can consume disk resources very quickly and adversely impact Traffic Server performance. 
+In addition to the standard and custom log file format, you can choose whether to
+save log files in binary or ASCII; refer to [Choosing Binary or ASCII](#ChoosingBinaryASCII).
+
+Event log files consume substantial disk space. Creating log entries in multiple formats
+at the same time can consume disk resources very quickly and adversely impact Traffic Server performance. 
 
 ### Using Standard Formats  ### {#UsingStandardFormats}
 
@@ -246,10 +241,10 @@ is produced for each `LogObject` definit
 * The **`LogFilter`** object defines a filter so that you include or exclude certain information from the log file. 
 * The **`LogObject`** object specifies all the information needed to produce a log file.
     * The name of the log file.  (required)
-    * The format to be used (required). This can be a standard format (Squid or Netscape) or  
+    * The format to be used (required). This can be a standard format (Squid or Netscape) or
     * a previously-defined custom format (i.e., a previously-defined `LogFormat` object). 
     * The file mode: `ASCII`, `Binary`, or `ASCII_PIPE`. The default is `ASCII`.   
-      The `ASCII_PIPE` mode writes log entries to a UNIX-named pipe (a buffer in memory);
+         The `ASCII_PIPE` mode writes log entries to a UNIX-named pipe (a buffer in memory);
       other processes can then read the data using standard I/O functions. The advantage of
       this option is that Traffic Server does not have to write to disk, which frees disk
       space and bandwidth for other tasks. When the buffer is full, Traffic Server drops
@@ -273,7 +268,9 @@ is produced for each `LogObject` definit
 1. In the [`records.config`](../configuration-files/records.config) file, edit the following variables
 2. [_`proxy.config.log.custom_logs_enabled`_](../configuration-files/records.config#proxy.config.log.custom_logs_enabled)
 5. In the [`logs_xml.config`](../configuration-files/logs_xml.config) file 
-6. Add [`LogFormat`](../configuration-files/logs_xml.config#LogFormat), [`LogFilter`](../configuration-files/logs_xml.config#LogFilters), and [`LogObject`](../configuration-files/logs_xml.config#LogObject) specifications to the configuration file.
+6. Add [`LogFormat`](../configuration-files/logs_xml.config#LogFormat),
+  [`LogFilter`](../configuration-files/logs_xml.config#LogFilters),
+  and [`LogObject`](../configuration-files/logs_xml.config#LogObject) specifications to the configuration file.
 7. Save and close the `log``s_xml.config` file. 
 9. Run the command `traffic_line -x` to apply your configuration changes. 
 
@@ -344,7 +341,7 @@ You can configure Traffic Server to crea
     By default, ASCII log files have a `.log` filename extension. 
 
 * **Binary**
-    
+
     These files generate lower system overhead and generally occupy less space on the
     disk than ASCII files (depending on the type of information being logged).
     However, you must use a converter application before you can read or analyze binary
@@ -384,7 +381,7 @@ standard tools. 
 
 To convert a binary log file to ASCII, use the `traffic_logcat` command
 The following is a description of its command-line options.   
-  
+
     Usage: traffic_logcat [-o output-file | -a] [-CEhSVw2] [input-file ...]
 
 `-o output_file`
@@ -397,7 +394,7 @@ The following is a description of its co
          traffic_logcat -a squid-1.blog squid-2.blog squid-3.blog
     generates 
 
-	 squid-1.log squid-2.log squid-3.log
+     squid-1.log squid-2.log squid-3.log
 
 `-S`
 :   Attempts to transform the input to Squid format, if possible.
@@ -411,8 +408,8 @@ The following is a description of its co
 `-2`
 :   Attempt to transform the input to Netscape Extended-2 format, if possible. 
 
-  
-**Note:** Use only one of the following options at any given time: `-S`, `-C`, `-E`, or` -2`.   
+
+**Note:** Use only one of the following options at any given time: `-S`, `-C`, `-E`, or` -2`.
 
 If no input files are specified, then `traffic_logcat` reads from the standard input (`stdin`).
 If you do not specify an output file, then `traffic_logcat` writes to the standard output (`stdout`). 
@@ -481,12 +478,12 @@ The following table describes the format
 `%S`
 :   The second in two-digit format, from 00-59. For example: 36.
 
-  
+
 
 The following is an example of a rolled log filename:
 
      squid.log.mymachine.20110912.12h00m00s-20000913.12h00m00s.old
-  
+
 The logging system buffers log records before writing them to disk.
 When a log file is rolled, the log buffer might be partially full.
 If it is, then the first entry in the new log file will have a timestamp
@@ -496,7 +493,7 @@ timestamp will be a lower bound for the 
 For example, suppose logs are rolled every three hours, and the first rolled log file is:
 
     squid.log.mymachine.20110912.12h00m00s-19980912.03h00m00s.old
-  
+
 If the lower bound for the first entry in the log buffer at 3:00:00 is 2:59:47, then the
 next log file will have the following timestamp when rolled:
 
@@ -568,7 +565,7 @@ ICP transactions in their own respective
 file contains the two origin servers `uni.edu` and `company.com` and Squid 
 format is enabled, then Traffic Server generates the following log files: 
 
-  
+
 `squid-uni.edu.log`
 :   All HTTP transactions for `uni.edu`
 
@@ -581,13 +578,13 @@ format is enabled, then Traffic Server g
 `squid.log`
 :   All HTTP transactions for other hosts
 
-  
+
 
 If you disable ICP log splitting, then ICP transactions are placed in the same 
 log file as HTTP transactions. Using the hosts and log format from the previous 
 example, Traffic Server generates the log files below:
 
-  
+
 `squid-uni.edu.log`
 :   All entries for `uni.edu`
 
@@ -597,7 +594,7 @@ example, Traffic Server generates the lo
 `squid.log`
 :   All other entries
 
-  
+
 
 Traffic Server also enables you to create XML-based [Custom Log Formats](#UsingCustomFormat) 
 that offer even greater control over log file generation. 
@@ -666,7 +663,7 @@ require manual collation. 
 
 **Note:** Log collation can have an impact on network performance. Because 
 all nodes are forwarding their log data buffers to the single collation server, 
-a bottleneck can occur.** **In addition, collated log files contain timestamp 
+a bottleneck can occur. In addition, collated log files contain timestamp 
 information for each entry, but entries in the files do not appear in strict 
 chronological order. You may want to sort collated log files before doing analysis. 
  
@@ -858,7 +855,6 @@ The following list describes each field.
 :   The proxy response content type; the object content type taken from the Traffic 
     Server response header.
 
-  
 
 ### Netscape Common  ### {#NetscapeCommon}
 
@@ -920,7 +916,7 @@ The following figure shows a sample log 
 
 ![sample log entry in common.log](/images/admin/netscape_extended_format.jpg)
 
-  
+
 `1`
 :   `chi`
 :   The IP address of the client’s host machine.
@@ -963,7 +959,7 @@ following list describes each field. 
 `17`
 :   `phr`
 :   The proxy hierarchy route; the route Traffic Server used to retrieve the object. 
-    
+
 
 `18`
 :   `cfsc`
@@ -978,7 +974,7 @@ following list describes each field. 
 `20`
 :   `crc`
 :   The cache result code; how the Traffic Server cache responded to the request: 
-    HIT, MISS, and so on. Cache result codes are described [here](XXX). 
-    
+    HIT, MISS, and so on. Cache result codes are described [here](../faq). 
+
 
  

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/index.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/actions-guide/index.en.mdtext Thu Sep  1 21:34:29 2011
@@ -59,39 +59,39 @@ Below is an example of typical usage for
         static int
         handler (TSCont contp, TSEvent event, void *edata)
         {
-        	if (event == TS_EVENT_IMMEDIATE) {
-        		TSAction actionp = TSNetConnect (contp, 127.0.0.1, 9999);
-        		if (!TSActionDone (actionp)) {
-        			TSContDataSet (contp, actionp);
-        		} else {
-        			/* We've already been called back... */
-        			return 0;
-        		}
-        	} else if (event == TS_EVENT_NET_CONNECT) {
-        		/* Net connection succeeded */
-        		TSContDataSet (contp, NULL);
-        		return 0;
-        	} else if (event == TS_EVENT_NET_CONNECT_FAILED) {
-        		/* Net connection failed */
-        		TSContDataSet (contp, NULL);
-        		return 0;
-        	} 
-        	return 0;
+            if (event == TS_EVENT_IMMEDIATE) {
+                TSAction actionp = TSNetConnect (contp, 127.0.0.1, 9999);
+                if (!TSActionDone (actionp)) {
+                    TSContDataSet (contp, actionp);
+                } else {
+                    /* We've already been called back... */
+                    return 0;
+                }
+            } else if (event == TS_EVENT_NET_CONNECT) {
+                /* Net connection succeeded */
+                TSContDataSet (contp, NULL);
+                return 0;
+            } else if (event == TS_EVENT_NET_CONNECT_FAILED) {
+                /* Net connection failed */
+                TSContDataSet (contp, NULL);
+                return 0;
+            } 
+            return 0;
         }
 
-       	void
+           void
         TSPluginInit (int argc, const char *argv[])
         {
-        	TSCont contp;
+            TSCont contp;
 
-        	contp = TSContCreate (handler, TSMutexCreate ());
+            contp = TSContCreate (handler, TSMutexCreate ());
 
-        	/* We don't want to call things out of TSPluginInit
-        	   directly since it's called before the rest of the
-        	   system is initialized. We'll simply schedule an event
-        	   on the continuation to occur as soon as the rest of
-        	   the system is started up. */
-        	TSContSchedule (contp, 0);
+            /* We don't want to call things out of TSPluginInit
+               directly since it's called before the rest of the
+               system is initialized. We'll simply schedule an event
+               on the continuation to occur as soon as the rest of
+               the system is started up. */
+            TSContSchedule (contp, 0);
         }
 
 
@@ -118,50 +118,50 @@ code implements this:
         static int
         handler (TSCont contp, TSEvent event, void *edata)
         {
-        	switch (event) {
-        		case (TS_EVENT_IMMEDIATE):
-        			TSContSchedule (contp, 30000);
-        			TSAction actionp = TSNetConnect(contp, 127.0.0.1, 9999);
-        			if (!TSActionDone (actionp)) {
-        				TSContDataSet (contp, actionp);
-        			} else {
-        				/* We've already been called back ... */
-        			}
-        			break;
-
-        		case (TS_EVENT_TIMEOUT):
-        			TSAction actionp = TSContDataGet (contp);
-        			if (!TSActionDone(actionp)) {
-        				TSActionCancel (actionp);
-        			}
-        			break;
-
-        		case (TS_EVENT_NET_CONNECT):
-        			/* Net connection succeeded */
-        			TSContDataSet (contp, NULL);
-        			break;
-
-        		case (TS_EVENT_NET_CONNECT_FAILED):
-        			/* Net connection failed */
-        			TSContDataSet (contp, NULL);
-        			break;
+            switch (event) {
+                case (TS_EVENT_IMMEDIATE):
+                    TSContSchedule (contp, 30000);
+                    TSAction actionp = TSNetConnect(contp, 127.0.0.1, 9999);
+                    if (!TSActionDone (actionp)) {
+                        TSContDataSet (contp, actionp);
+                    } else {
+                        /* We've already been called back ... */
+                    }
+                    break;
+
+                case (TS_EVENT_TIMEOUT):
+                    TSAction actionp = TSContDataGet (contp);
+                    if (!TSActionDone(actionp)) {
+                        TSActionCancel (actionp);
+                    }
+                    break;
+
+                case (TS_EVENT_NET_CONNECT):
+                    /* Net connection succeeded */
+                    TSContDataSet (contp, NULL);
+                    break;
+
+                case (TS_EVENT_NET_CONNECT_FAILED):
+                    /* Net connection failed */
+                    TSContDataSet (contp, NULL);
+                    break;
 
-        	} 
-        	return 0;
+            } 
+            return 0;
         }
 
-      	void
+          void
         TSPluginInit (int argc, const char *argv[])
         {
-        	TSCont contp;
+            TSCont contp;
 
-        	contp = TSContCreate (handler, TSMutexCreate ());
-        	/* We don't want to call things out of TSPluginInit
-        	   directly since it's called before the rest of the
-        	   system is initialized. We'll simply schedule an event
-        	   on the continuation to occur as soon as the rest of
-        	   the system is started up. */
-        	TSContSchedule (contp, 0);
+            contp = TSContCreate (handler, TSMutexCreate ());
+            /* We don't want to call things out of TSPluginInit
+               directly since it's called before the rest of the
+               system is initialized. We'll simply schedule an event
+               on the continuation to occur as soon as the rest of
+               the system is started up. */
+            TSContSchedule (contp, 0);
         }
 
 The action functions are:

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/adding-statistics/coupled-statistics.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/adding-statistics/coupled-statistics.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/adding-statistics/coupled-statistics.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/adding-statistics/coupled-statistics.en.mdtext Thu Sep  1 21:34:29 2011
@@ -77,39 +77,39 @@ via `TSStatCoupledLocalCopyDestroy`.
 ### Example Using the redirect-1.c Sample Plugin ### {#ExampleUsingredirect-1.cSamplePlugin}
 
         :::c
-	static TSCoupledStat request_outcomes;
-	
-	static TSStat requests_all;
-	static TSStat requests_redirects;
-	static TSStat requests_unchanged;
-	
-	request_outcomes = TSStatCoupledGlobalCategoryCreate ("request_outcomes"); 
-	
-	requests_all = TSStatCoupledGlobalAdd (request_outcomes, "requests.all", TSSTAT_TYPE_FLOAT);
-	requests_redirects = TSStatCoupledGlobalAdd (request_outcomes, "requests.redirects",
-	    TSSTAT_TYPE_INT64);
-	requests_unchanged = TSStatCoupledGlobalAdd (request_outcomes, "requests.unchanged", 
-	    TSSTAT_TYPE_INT64);
-	
-	TSCoupledStat local_request_outcomes;
-	TSStat local_requests_all;
-	TSStat local_requests_redirects;
-	TSStat local_requests_unchanged;
-	
-	local_request_outcomes = TSStatCoupledLocalCopyCreate("local_request_outcomes", 
-	    request_outcomes); 
-	local_requests_all = TSStatCoupledLocalAdd(local_request_outcomes, "requests.all.local", 
-	    TSSTAT_TYPE_FLOAT);
-	local_requests_redirects = TSStatCoupledLocalAdd(local_request_outcomes, 
-	    "requests.redirects.local", TSSTAT_TYPE_INT64);
-	local_requests_unchanged = TSStatCoupledLocalAdd(local_request_outcomes, 
-	    "requests.unchanged.local", TSSTAT_TYPE_INT64);
-	
-	TSStatFloatAddTo( local_requests_all, 1.0 ) ; 
-	...
-	TSStatIncrement (local_requests_unchanged); 
-	TSStatsCoupledUpdate(local_request_outcomes); 
-	
-	TSStatCoupledLocalCopyDestroy(local_request_outcomes); 
+    static TSCoupledStat request_outcomes;
+    
+    static TSStat requests_all;
+    static TSStat requests_redirects;
+    static TSStat requests_unchanged;
+    
+    request_outcomes = TSStatCoupledGlobalCategoryCreate ("request_outcomes"); 
+    
+    requests_all = TSStatCoupledGlobalAdd (request_outcomes, "requests.all", TSSTAT_TYPE_FLOAT);
+    requests_redirects = TSStatCoupledGlobalAdd (request_outcomes, "requests.redirects",
+        TSSTAT_TYPE_INT64);
+    requests_unchanged = TSStatCoupledGlobalAdd (request_outcomes, "requests.unchanged", 
+        TSSTAT_TYPE_INT64);
+    
+    TSCoupledStat local_request_outcomes;
+    TSStat local_requests_all;
+    TSStat local_requests_redirects;
+    TSStat local_requests_unchanged;
+    
+    local_request_outcomes = TSStatCoupledLocalCopyCreate("local_request_outcomes", 
+        request_outcomes); 
+    local_requests_all = TSStatCoupledLocalAdd(local_request_outcomes, "requests.all.local", 
+        TSSTAT_TYPE_FLOAT);
+    local_requests_redirects = TSStatCoupledLocalAdd(local_request_outcomes, 
+        "requests.redirects.local", TSSTAT_TYPE_INT64);
+    local_requests_unchanged = TSStatCoupledLocalAdd(local_request_outcomes, 
+        "requests.unchanged.local", TSSTAT_TYPE_INT64);
+    
+    TSStatFloatAddTo( local_requests_all, 1.0 ) ; 
+    ...
+    TSStatIncrement (local_requests_unchanged); 
+    TSStatsCoupledUpdate(local_request_outcomes); 
+    
+    TSStatCoupledLocalCopyDestroy(local_request_outcomes); 
 
 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/index.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/index.en.mdtext Thu Sep  1 21:34:29 2011
@@ -81,17 +81,17 @@ avoid accessing something that has been 
 Below is an example, followed by an explanation.
 
         ::::c
-	continuation_handler (TSCont contp, TSEvent event, void *edata) {
-		switch (event) {
-			case event1:
-				TSReentrantCall (contp);
-				/* Return right away after this call */
-				break;
-			case event2:
-				TSContDestroy (contp);
-				break;
-		}
-	}
+    continuation_handler (TSCont contp, TSEvent event, void *edata) {
+        switch (event) {
+            case event1:
+                TSReentrantCall (contp);
+                /* Return right away after this call */
+                break;
+            case event2:
+                TSContDestroy (contp);
+                break;
+        }
+    }
 
 The above example first assumes that the continuation is called back with `event1`; 
 it then does the first reentrant call that schedules the continuation to receive 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/writing-handler-functions.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/writing-handler-functions.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/writing-handler-functions.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/continuations/writing-handler-functions.en.mdtext Thu Sep  1 21:34:29 2011
@@ -34,20 +34,20 @@ handler function typically has a switch 
         ::::c
         static int some_handler (TScont contp, TSEvent event, void *edata)
         {
-        	.....
-        		switch(event) {
-        			case TS_EVENT_SOME_EVENT_1:
-        				do_some_thing_1;
-        				return;
-        			case TS_EVENT_SOME_EVENT_2:
-        				do_some_thing_2;
-        				return;
-        			case TS_EVENT_SOME_EVENT_3:
-        				do_some_thing_3;
-        				return;
-        			default: break;
-        		}
-        	return 0;
+            .....
+                switch(event) {
+                    case TS_EVENT_SOME_EVENT_1:
+                        do_some_thing_1;
+                        return;
+                    case TS_EVENT_SOME_EVENT_2:
+                        do_some_thing_2;
+                        return;
+                    case TS_EVENT_SOME_EVENT_3:
+                        do_some_thing_3;
+                        return;
+                    default: break;
+                }
+            return 0;
         }
 
 
@@ -154,12 +154,12 @@ passed to handler functions:
 :   Error code, see `TS_CACHE_ERROR_XXX`
 
 `TS_EVENT_NET_ACCEPT`
-:   	TSNetAccept, TSHttpTxnServerIntercept,
-    	              TSHttpTxnIntercept:   Net VConnection
+:       TSNetAccept, TSHttpTxnServerIntercept,
+                      TSHttpTxnIntercept:   Net VConnection
 
 `TS_EVENT_NET_ACCEPT_FAILED`
-:   	TSNetAccept, TSHttpTxnServerIntercept,
-    	              TSHttpTxnIntercept:   Nothing
+:       TSNetAccept, TSHttpTxnServerIntercept,
+                      TSHttpTxnIntercept:   Nothing
 
 `TS_EVENT_HOST_LOOKUP`
 :   `TSHostLookup`

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/a-simple-plugin.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/a-simple-plugin.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/a-simple-plugin.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/a-simple-plugin.en.mdtext Thu Sep  1 21:34:29 2011
@@ -44,11 +44,11 @@ shared libraries on all the supported Tr
 Assuming the sample program is stored in the file `hello-world.c`, you could
 use the following commands to build a shared library
 
-	tsxs -o hello-world.so -c hello-world.c
+    tsxs -o hello-world.so -c hello-world.c
 
 This shared library will be your plugin. In order to install it, run
 
-	sudo tsxs -o hello-world.so -i
+    sudo tsxs -o hello-world.so -i
 
 or the equivalent to `sudo` on your platform.
 
@@ -58,8 +58,8 @@ Your next step is to tell Traffic Server
 line to the `plugin.config` file. Since our simple plugin does not require
 any arguments, the following `plugin.config` will work:
 
-	# a simple plugin.config for hello-world
-	hello-world.so
+    # a simple plugin.config for hello-world
+    hello-world.so
 
 Traffic Server can accommodate multiple plugins. If several plugin functions
 are triggered by the same event, then Traffic Server invokes each plugin's
@@ -84,17 +84,17 @@ is common to use the default directory. 
 The last step is to start/restart Traffic Server. Shown below is the output
 displayed after you've created and loaded your `hello-world` plugin.
 
-	# grep proxy.config.plugin.plugin_dir config/records.config
-	CONFIG proxy.config.plugin.plugin_dir STRING config/plugins
-	# ls config/plugins
-	hello-world.so*
-	# bin/traffic_server
-	[Mar 27 19:06:31.669] NOTE: updated diags config
-	[Mar 27 19:06:31.680] NOTE: loading plugin 'config/plugins/hello-world.so'
-	hello world
-	[Mar 27 19:06:32.046] NOTE: cache disabled (initializing)
-	[Mar 27 19:06:32.053] NOTE: cache enabled
-	[Mar 27 19:06:32.526] NOTE: Traffic Server running
+    # grep proxy.config.plugin.plugin_dir config/records.config
+    CONFIG proxy.config.plugin.plugin_dir STRING config/plugins
+    # ls config/plugins
+    hello-world.so*
+    # bin/traffic_server
+    [Mar 27 19:06:31.669] NOTE: updated diags config
+    [Mar 27 19:06:31.680] NOTE: loading plugin 'config/plugins/hello-world.so'
+    hello world
+    [Mar 27 19:06:32.046] NOTE: cache disabled (initializing)
+    [Mar 27 19:06:32.053] NOTE: cache enabled
+    [Mar 27 19:06:32.526] NOTE: Traffic Server running
 
 **Note:** in the example above, Traffic Server notes are directed to the console
 by specifying `E` for `proxy.config.diags.output.note ` in `records.config`.

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/index.en.mdtext Thu Sep  1 21:34:29 2011
@@ -151,10 +151,10 @@ is where you installed Traffic Server.
 The sample `plugin.config` file below contains a comment line, a blank line, 
 and two plugin configurations:
 
-	# This is a comment line.
-	
-	my-plugin.so junk.example.com trash.example.org garbage.example.edu
-	some-plugin.so arg1 arg2 $proxy.config.http.cache.on
+    # This is a comment line.
+    
+    my-plugin.so junk.example.com trash.example.org garbage.example.edu
+    some-plugin.so arg1 arg2 $proxy.config.http.cache.on
 
 Each plugin configuration in the `plugin.config` file resembles a UNIX or DOS
 shell command; each line in `plugin.config` cannot exceed 1023 characters.
@@ -169,20 +169,20 @@ variable and substitute its value.
 Plugins with global variables should not appear more than once in `plugin.config`.
 For example, if you enter:
 
-	add-header.so header1
-	add-header.so header2
+    add-header.so header1
+    add-header.so header2
 
 then the second global variable, `header2`, will be used for both instances.
 A simple workaround is to give different names to different instances of the
 same plugin. For example:
 
-	cp add-header.so add-header1.so
-	cp add-header.so add-header2.so
+    cp add-header.so add-header1.so
+    cp add-header.so add-header2.so
 
 These entries will produce the desired result below:
 
-	add-header1.so header1
-	add-header2.so header2
+    add-header1.so header1
+    add-header2.so header2
 
 
 ### Configuration File Rules

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/plugin-registration-and-version-checking.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/plugin-registration-and-version-checking.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/plugin-registration-and-version-checking.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/getting-started/plugin-registration-and-version-checking.en.mdtext Thu Sep  1 21:34:29 2011
@@ -31,55 +31,55 @@ running with a compatible version of Tra
 
 
         :::c
-	#include <stdio.h>
-	#include <ts/ts.h>
-	int
-	check_ts_version()
-	{
-	
-	 const char *ts_version = TSTrafficServerVersionGet();
-	 int result = 0;
-	
-	   if (ts_version) {
-	    int major_ts_version = 0;
-	    int minor_ts_version = 0;
-	    int patch_ts_version = 0;
-	
-	   if (sscanf(ts_version, "%d.%d.%d", &major_ts_version,
-	      &minor_ts_version, &patch_ts_version) != 3) {
-	      return 0;
-	  }
-	
-	  /* We need at least Traffic Server 2.0 */
-	
-	   if (major_ts_version >= 2) {
-	      result = 1;
-	   }
-	   
-	  }
-	
-	  return result;
-	}
-	
-	void
-	TSPluginInit (int argc, const char *argv[])
-	{
-	
-	      TSPluginRegistrationInfo info;
-	
-	      info.plugin_name = "hello-world";
-	      info.vendor_name = "MyCompany";
-	      info.support_email = "ts-api-support@MyCompany.com";
-	
-	      if (!TSPluginRegister (TS_SDK_VERSION_2_0 , &info)) {
-	         TSError ("Plugin registration failed. \n");
-	      }
-	
-	      if (!check_ts_version()) {
-	         TSError ("Plugin requires Traffic Server 2.0 or later\n");
-	         return;
-	      }
-	
-	      TSDebug ("debug-hello", "Hello World!\n");
-	}
+    #include <stdio.h>
+    #include <ts/ts.h>
+    int
+    check_ts_version()
+    {
+    
+     const char *ts_version = TSTrafficServerVersionGet();
+     int result = 0;
+    
+       if (ts_version) {
+        int major_ts_version = 0;
+        int minor_ts_version = 0;
+        int patch_ts_version = 0;
+    
+       if (sscanf(ts_version, "%d.%d.%d", &major_ts_version,
+          &minor_ts_version, &patch_ts_version) != 3) {
+          return 0;
+      }
+    
+      /* We need at least Traffic Server 2.0 */
+    
+       if (major_ts_version >= 2) {
+          result = 1;
+       }
+       
+      }
+    
+      return result;
+    }
+    
+    void
+    TSPluginInit (int argc, const char *argv[])
+    {
+    
+          TSPluginRegistrationInfo info;
+    
+          info.plugin_name = "hello-world";
+          info.vendor_name = "MyCompany";
+          info.support_email = "ts-api-support@MyCompany.com";
+    
+          if (!TSPluginRegister (TS_SDK_VERSION_2_0 , &info)) {
+             TSError ("Plugin registration failed. \n");
+          }
+    
+          if (!check_ts_version()) {
+             TSError ("Plugin requires Traffic Server 2.0 or later\n");
+             return;
+          }
+    
+          TSDebug ("debug-hello", "Hello World!\n");
+    }
 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/implementing-the-handler-and-getting-a-handle-to-the-transaction.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/implementing-the-handler-and-getting-a-handle-to-the-transaction.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/implementing-the-handler-and-getting-a-handle-to-the-transaction.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/implementing-the-handler-and-getting-a-handle-to-the-transaction.en.mdtext Thu Sep  1 21:34:29 2011
@@ -21,25 +21,25 @@ Notice:    Licensed to the Apache Softwa
 The handler function for the plugin's parent continuation is implemented as
 follows:
 
-	:::c
-	static int
-	auth_plugin (TSCont contp, TSEvent event, void *edata)
-	{
-	
-	     TSHttpTxn txnp = (TSHttpTxn) edata;
-	     switch (event) {
-	     case TS_EVENT_HTTP_OS_DNS:
-	          handle_dns (txnp, contp);
-	          return 0;
-	     case TS_EVENT_HTTP_SEND_RESPONSE_HDR:
-	          handle_response (txnp);
-	          return 0;
-	     default:
-	          break;
-	     }
-	
-	     return 0;
-	}
+    :::c
+    static int
+    auth_plugin (TSCont contp, TSEvent event, void *edata)
+    {
+    
+         TSHttpTxn txnp = (TSHttpTxn) edata;
+         switch (event) {
+         case TS_EVENT_HTTP_OS_DNS:
+              handle_dns (txnp, contp);
+              return 0;
+         case TS_EVENT_HTTP_SEND_RESPONSE_HDR:
+              handle_response (txnp);
+              return 0;
+         default:
+              break;
+         }
+    
+         return 0;
+    }
 
 
 

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/setting-a-transaction-hook.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/setting-a-transaction-hook.en.mdtext?rev=1164283&r1=1164282&r2=1164283&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/setting-a-transaction-hook.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/sdk/header-based-plugin-examples/basic-authorization-plugin/setting-a-transaction-hook.en.mdtext Thu Sep  1 21:34:29 2011
@@ -28,10 +28,10 @@ the request.
 In the `handle_dns` routine, the following lines handle the authorization
 error case:
 
-	:::c
-	done:
-	     TSHttpTxnHookAdd (txnp, TS_HTTP_SEND_RESPONSE_HDR_HOOK, contp);
-	     TSHttpTxnReenable (txnp, TS_EVENT_HTTP_ERROR);
+    :::c
+    done:
+         TSHttpTxnHookAdd (txnp, TS_HTTP_SEND_RESPONSE_HDR_HOOK, contp);
+         TSHttpTxnReenable (txnp, TS_EVENT_HTTP_ERROR);
 
 If `handle_dns` does not find the `Proxy-Authorization` field set to Basic
 authorization or a valid username/password, then it adds a `SEND_RESPONSE_HDR_HOOK`



Mime
View raw message