trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1070302 [1/4] - in /trafficserver/site/branches/ats-cms/content/docs/trunk: ./ admin/ admin/configuration-files/ admin/configuring-cache/ admin/configuring-traffic-server/ admin/event-logging-formats/ admin/explicit-proxy-caching/ admin/fa...
Date Sun, 13 Feb 2011 21:38:38 GMT
Author: igalic
Date: Sun Feb 13 21:38:37 2011
New Revision: 1070302

URL: http://svn.apache.org/viewvc?rev=1070302&view=rev
Log:
Adding basic content migration for admin guide:
h2md http://old-url | psed 's/INK/TS/g' > index.en.mdtext
Broke the chapters up into multiple directories

Added:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/files.en.mdtext
      - copied unchanged from r1068220, trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-traffic-server/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-traffic-server/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/getting-started/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/getting-started/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/hierachical-caching/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/http-proxy-caching/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/http-proxy-caching/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/reverse-proxy-http-redirects/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/
Removed:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/files.en.mdtext
Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS

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=1070302&r1=1070301&r2=1070302&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS Sun Feb 13 21:38:37 2011
@@ -17,8 +17,6 @@ To Do List
 
 - invent a wheel that will help translators and users spot out-dated documents
 
-- migrate the content - SDK is done. Admin guide is pending.
-
 - update the content: https://issues.apache.org/jira/secure/IssueNavigator.jspa?component=12313124
 
 
@@ -42,6 +40,21 @@ Migration procedure
   https://issues.apache.org/jira/browse/TS-538 and it's ink-2-ts.sh
 
 
+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*
+
+
+
 Findings
 =================
 

Added: 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=1070302&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext Sun Feb 13 21:38:37 2011
@@ -0,0 +1,361 @@
+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
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+
+   
+
+    
+      
+    
+
+ [![](/images/ts75.png)](/index.html)™
+      
+
+# Administrator's Guide # {#AdministratorsGuide}
+
+    
+
+   
+
+   
+
+      
+
+         
+
+            
+
+# Configuring the Cache # {#ConfiguringCache}
+
+The Traffic Server cache consists of a high-speed object database called the 
+**object store **that indexes objects according to URLs and their associated 
+headers.
+
+This chapter discusses the following topics: 
+
+* [The Traffic Server Cache](#TrafficEdgeCache)
+* [The RAM Cache](#RAMCache)
+* [Changing the Size of the RAM Cache](#ChangingSizeRAMCache)
+* [Changing Cache Capacity](#ChangingCacheCapacity)
+* [Partitioning the Cache](#PartitioningCache)
+* [Configuring the Cache Object Size Limit](#ConfiguringCacheObjectSizeLimit)
+* [Clearing the Cache](#ClearingCache)
+* [Removing an Object From the Cache](#RemoveObjectFromCache)
+* [Inspecting the Cache](#InspectingCache)
+
+## The Traffic Server Cache ## {#TSCache}
+
+The Traffic Server cache consists of a high-speed object database called the 
+**object store**. The object store indexes objects according to URLs and associated 
+headers. This enables Traffic Server to store, retrieve, and serve not only 
+web pages, but also parts of web pages - which provides optimum bandwidth savings. 
+Using sophisticated object management, the object store can cache alternate 
+versions of the same object (versions may differ because of dissimilar language 
+or encoding types). It can also efficiently store very small and very large 
+documents, thereby minimizing wasted space. When the cache is full, Traffic 
+Server removes stale data to ensure the most requested objects are kept readily 
+available and fresh. 
+
+Traffic Server is designed to tolerate total disk failures on any of the cache 
+disks. If the disk fails completely, then Traffic Server marks the entire disk 
+as corrupt and continues using the remaining disks. An alarm is then created 
+to indicate which disk failed. If all of the cache disks fail, then Traffic 
+Server goes into proxy-only mode. 
+
+You can perform the following cache configuration tasks: 
+
+* Change the total amount of disk space allocated to the cache: refer to [Changing Cache Capacity](#ChangingCacheCapacity). 
+* Partition the cache by reserving cache disk space for specific protocols and origin servers/domains: refer to [Partitioning the Cache](#PartitioningCache). 
+* Delete all data in the cache: refer to [Clearing the Cache](#ClearingCache).
+
+## The RAM Cache ## {#RAMCache}
+
+Traffic Server maintains a small RAM cache of extremely popular objects. This 
+RAM cache serves the most popular objects as quickly as possible and reduces 
+load on disks, especially during temporary traffic peaks. You can configure 
+the RAM cache size to suit your needs, as described in [Changing the Size of 
+the RAM Cache](#ChangingSizeRAMCache) below. 
+
+## Changing the Size of the RAM Cache ## {#ChangingSizeofRAMCache}
+
+Traffic Server provides a dedicated RAM cache for fast retrieval of popular 
+small objects. The default RAM cache size is automatically calculated based 
+on the number and size of the cache partitions you have configured. If you've 
+partitioned your cache according to protocol and/or hosts, then the size of 
+the RAM cache for each partition is proportional to the size of that partition. 
+ 
+
+You can increase the RAM cache size for better cache hit performance. However, 
+if you increase the size of the RAM cache and observe a decrease in performance 
+(such as increased latencies), then it's possible that the operating system 
+requires more memory for network resources. In such instances, you should return 
+the RAM cache size to its previous value.
+
+##### To change the RAM cache size:  ##### {#changeRAMcachesize}
+
+1. Stop Traffic Server. 
+2. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+3. Edit the following variable:
+4. **Variable** **Description** 
+_`proxy.config.cache.ram_cache.size`_
+:   Set this variable to specify the size of the RAM cache.  
+		 The default value of -1 means that the RAM cache is automatically sized at approximately 1MB per gigabyte of disk.
+
+5. Save and close the `records.config` file. 
+6. Restart Traffic Server. If you increase the RAM cache to a size or 1GB or more, then restart with the `start_traffic_server` command (refer to [Starting Traffic Server](getstart.htm#StartingTrafficEdge)). 
+
+ 
+
+## Changing Cache Capacity ## {#ChangingCacheCapacity}
+
+You can increase or reduce the total amount of disk space allocated to the 
+cache without clearing the content. To check the size of the cache (in bytes), 
+enter the command `traffic_line -r proxy.process.cache.bytes_total`. 
+
+### Increasing Cache Capacity  ### {#IncreasingCacheCapacity}
+
+To increase the total amount of disk space allocated to the cache on existing 
+disks or to add new disks to a Traffic Server node, follow the steps below: 
+
+1. Stop Traffic Server. 
+2. Add hardware, if necessary. 
+3. Edit the Traffic Server `storage.config` file: increase the amount of disk space allocated to the cache on existing disks or describe the new hardware you are adding (refer to [storage.config](files.htm#storage.config)).
+4. If you add a new disk, then you must edit the `/etc/rc.d/init.d/traffic_server` file to add a raw disk binding. Instructions for adding a raw disk binding are located in the Traffic Server `storage.config` file. 
+5. Restart Traffic Server. 
+
+### Reducing Cache Capacity  ### {#ReducingCacheCapacity}
+
+To reduce the total amount of disk space allocated to the cache on an existing 
+disk or to remove disks from a Traffic Server node, follow the steps below: 
+
+1. Stop Traffic Server. 
+2. Remove hardware, if necessary. 
+3. Edit the Traffic Server `storage.config` file: reduce the amount of disk space allocated to the cache on existing disks or delete the reference to the hardware you're removing (refer to [storage.config](files.htm#storage.config)). 
+4. If you remove a disk, then you must edit the `/etc/rc.d/init.d/traffic_server` file to remove the raw disk binding for the disk. 
+5. Restart Traffic Server. 
+
+**IMPORTANT:** In the `storage.config` file, a formatted or raw disk must be 
+at least 128 MB. 
+
+## Partitioning the Cache ## {#PartitioningCache}
+
+You can manage your cache space more efficiently and restrict disk usage by 
+creating cache partitions with different sizes for specific protocols. You 
+can further configure these partitions to store data from specific origin servers 
+and/or domains. The partition configuration must be the same on all nodes in 
+a cluster. 
+
+### Creating Cache Partitions for Specific Protocols ### {#CreatingCachePartitionsforSpecificProtocols}
+
+You can create separate partitions for your cache that vary in size to store 
+content according to protocol. This ensures that a certain amount of disk space 
+is always available for a particular protocol. Traffic Server currently supports 
+the **http** partition type for HTTP objects.
+
+##### To partition the cache according to protocol:  ##### {#partitioncacheaccordingprotocol}
+
+1. In a text editor, open the `partition.config` file located in the Traffic Server `config` directory. 
+2. Enter a line in the file for each partition you want to create (refer to [partition.config](files.htm#partition.config)). 
+3. Save and close the `partition.config` file. 
+4. Restart Traffic Server. 
+
+#### Making Changes to Partition Sizes and Protocols  #### {#MakingChangesPartitionSizesProtocols}
+
+After you've configured your cache partitions based on protocol, you can make 
+changes to the configuration at any time. Before making changes, note the following: 
+ 
+
+* You must stop Traffic Server before you change the cache partition size and protocol assignment. 
+* When you increase the size of a partition, the contents of the partition are _not_ deleted However, when you reduce the size of a partition, the contents of the partition _are_ deleted. 
+* When you change the partition number, the partition is deleted and then recreated, even if the size and protocol type remain the same. 
+* When you add new disks to your Traffic Server node, partition sizes specified in percentages will increase proportionately. 
+* A lot of changes to partition sizes might result in disk fragmentation, which affects performance and hit rate. You should clear the cache before making many changes to cache partition sizes (refer to [Clearing the Cache](#ClearingCache)).
+
+### Partitioning the Cache According to Origin Server or Domain ### {#PartitioningCacheAccordingOriginServerDomain}
+
+After you have partitioned the cache according to size and protocol, you can 
+assign the partitions you created to specific origin servers and/or domains. 
+You can assign a partition to a single origin server or to multiple origin 
+servers. However, if a partition is assigned to multiple origin servers, then 
+there is no guarantee on the space available in the partition for each origin 
+server. Content is stored in the partition according to popularity. In addition 
+to assigning partitions to specific origin servers and domains, you must assign 
+a generic partition to store content from all origin servers and domains that 
+are not listed. This generic partition is also used if the partitions for a 
+particular origin server or domain become corrupt. If you do not assign a generic 
+partition, then Traffic Server will run in proxy-only mode. 
+
+**Note: **You do _not_ need to stop Traffic Server before you assign partitions 
+to particular hosts or domains. However, this type of configuration is time-consuming 
+and can cause a spike in memory usage. Therefore, it's best to configure partition 
+assignment during periods of low traffic. 
+
+##### To partition the cache according to hostname and domain:  ##### {#partitioncacheaccordinghostnamedomain}
+
+1. Configure the cache partitions according to size and protocol, as described in [Creating Cache Partitions for Specific Protocols](#CreatingCachePartitionsSpecificProtocols). 
+2. Create a separate partition based on protocol for each host and domain, as well as an additional generic partition to use for content that does not belong to these origin servers or domains. The partitions do not need to be the same size. 
+3. In a text editor, open the `hosting.config` file located in the Traffic Server `config` directory. 
+4. Enter a line in the file to allocate the partition(s) used for each origin server and/or domain (refer to [hosting.config](files.htm#hosting.config)). 
+5. Assign a generic partition to use for content that does not belong to any of the origin servers or domains listed in the file. If all partitions for a particular origin server become corrupt, then Traffic Server will also use the generic partition to store content for that origin server (see [hosting.config](files.htm#hosting.config)). 
+6. Save and close the `hosting.config` file. 
+7. Navigate to the Traffic Server `bin` directory. 
+8. Run the command `traffic_line -x` to apply the configuration changes. 
+
+## Configuring the Cache Object Size Limit ## {#ConfiguringCacheObjectSizeLimit}
+
+By default, Traffic Server allows objects of any size to be cached. You can 
+change the default behavior and specify a size limit for objects in the cache 
+via the steps below:
+
+1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+2. Edit the following variable:  
+**Variable** **Description** 
+`_proxy.config.cache.max_doc_size_`
+:   Set this variable to specify the maximum size allowed for objects in the cache in bytes.  
+		 Enter `0` (zero) if you do not want a size limit.
+
+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. 
+
+## Clearing the Cache ## {#ClearingCache}
+
+When you clear the cache, you remove all data from the entire cache - including 
+data in the host database. You should clear the cache before performing certain 
+cache configuration tasks, such as partitioning. You cannot clear the cache 
+when Traffic Server is running. 
+
+##### To clear the cache:  ##### {#clearcache}
+
+1. Stop Traffic Server (refer to [Stopping Traffic Server](getstart.htm#StoppingTrafficEdge)). 
+2. Enter the following command to clear the cache:  
+`traffic_server -Cclear`  
+The `clear` command deletes all data in the object store and the host database. Traffic Server does not prompt you to confirm the deletion. 
+3. Restart Traffic Server (refer to [Starting Traffic Server](getstart.htm#StartingTrafficEdge)).
+
+## Removing an Object From the Cache ## {#RemovinganObjectFromCache}
+
+Traffic Server accepts the custom HTTP request method `PURGE` when removing 
+a specific object from cache. If the object is found in the cache and is successfully 
+removed, then Traffic Server responds with a `200 OK ` HTTP message; otherwise, 
+a `404 File Not Found` message is returned. 
+
+In the following example, Traffic Server is running on the domain _`example.com`_ 
+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
+
+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 
+the Traffic Server cache).
+
+Note: The procedure above only removes an object from a _specific_ Traffic 
+Server cache. Users may still see the old (removed) content if it was cached 
+by intermediary caches or by the end-users' web browser.
+
+## Inspecting the Cache ## {#InspectingCache}
+
+Traffic Server provides a Cache Inspector utility that enables you to view, 
+delete, and invalidate URLs in the cache (HTTP only). The Cache Inspector utility 
+is a powerful tool that's capable of deleting _all_ the objects in your cache; 
+therefore, make sure that only authorized administrators are allowed to access 
+this utility. To control which hosts have access via the `mgmt_allow.config` 
+file, see [Controlling Host Access to Traffic Manager](secure.htm#ControllingHostAccessTrafficManager). 
+ 
+
+### Accessing the Cache Inspector Utility  ### {#AccessingCacheInspectorUtility}
+
+To access the Cache Inspector utility, follow the steps below:
+
+1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+2. Add the following variable at the end of the file:  
+`_CONFIG proxy.config.http_ui_enabled INT 1_`
+3. To access the cache inspector in reverse proxy mode, you must add a remap rule to `remap.config` to expose the URL.   
+ For example:   
+`map http://yourhost.com/myCI http://{cache} @action=allow @src_ip=corp_internal_address`
+4. From the Traffic Server `bin` directory, enter the following command to re-read the configuration file:  
+`traffic_line -x`
+5. Open your web browser and configure it to use your Traffic Server as a proxy server. Type the following URL:   
+`http://{cache}`
+6. The Cache page opens (see [Using the Cache Page](#UsingCachePage) below).
+
+### Using the Cache Page  ### {#UsingCachePage}
+
+The **Cache page** provides several options that enable you to view and delete 
+the contents of your cache: 
+
+* Click **Lookup url** to search for a particular URL in the cache. When Traffic Server finds the URL in the cache, it displays details about the object that corresponds to the URL (such as the header length and the number of alternates). From the display page, you can delete the URL from the cache. 
+* Click **Delete url** to delete a particular URL or list of URLs from the cache. Traffic Server indicates if a delete is successful. 
+* Click **Regex lookup** to search for URLs that match one or more regular expressions. From the display page, you can delete the URLs listed.  
+ For example, enter the following to search for all URLs that end in html and are prefixed with 	http://www.dianes.com: 
+		  http://www.dianes.com/.*\.html$
+* Click **Regex delete** to delete all URLs that match a specified regular expression.  
+ For example, enter the following to delete all HTTP URLs that end in `html`:   
+`http://.*\.html$` 
+* Click **Regex invalidate** to invalidate URLs that match a specified regular expression. When you invalidate a URL, Traffic Server marks the object that corresponds to the URL as stale in the cache. Traffic Server then contacts the origin server to check if the object is still fresh (revalidates) before serving it from the cache. 
+
+**Note:** Only one administrator should delete and invalidate cache entries 
+from the Cache page at any point in time. Changes made by multiple administrators 
+at the same time can lead to unpredictable results.
+
+         
+
+      
+
+   
+
+   
+
+         
+
+* [Overview](intro.htm)
+* [Getting Started](getstart.htm)
+* [HTTP Proxy Caching ](http.htm)
+* [Explicit Proxy Caching](explicit.htm)
+* [Reverse Proxy and HTTP Redirects](reverse.htm)
+* [Hierarchical Caching](hier.htm)
+* [Configuring the Cache](cache.htm)
+* [Monitoring Traffic](monitor.htm)
+* [Configuring Traffic Server](configure.htm)
+* [Security Options](secure.htm)
+* [Working with Log Files](log.htm)
+* [Traffic Line Commands](cli.htm)
+* [Event Logging Formats](logfmts.htm)
+* [Configuration Files](files.htm) 
+* [Traffic Server Error Messages](errors.htm)
+* [FAQ and Troubleshooting Tips](trouble.htm)
+* [Traffic Server 管理员指南](ts_admin_chinese.pdf) (PDF)
+
+   
+
+   
+
+ Copyright © 2011 [The Apache Software Foundation](http://www.apache.org/). 
+Licensed under the [Apache License](http://www.apache.org/licenses/), Version 
+2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the 
+Apache feather logo are trademarks of The Apache Software Foundation.
+
+
+

Added: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-traffic-server/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-traffic-server/index.en.mdtext?rev=1070302&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-traffic-server/index.en.mdtext (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-traffic-server/index.en.mdtext Sun Feb 13 21:38:37 2011
@@ -0,0 +1,132 @@
+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
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+
+   
+
+    
+      
+    
+
+ [![](/images/ts75.png)](/index.html)™
+      
+
+# Administrator's Guide # {#AdministratorsGuide}
+
+    
+
+   
+
+   
+
+      
+
+         
+
+            
+
+# Configuring Traffic Server # {#ConfiguringTS}
+
+Traffic Server provides several options for configuring the system.
+
+This chapter discusses the following topics: 
+
+* [Configure Traffic Server Using Traffic Line](#ConfiguringTrafficEdgeUsingTrafficLine)
+* [Configure Traffic Server Using Configuration Files](#ConfiguringTrafficEdgeUsingConfigFiles)
+
+## Configure Traffic Server Using Traffic Line ## {#ConfigureTSUsingTrafficLine}
+
+Traffic Line enables you to quickly and easily change your Traffic Server configuration 
+via command-line interface. Alternatively, you can also use [Traffic Shell](getstart.htm#StartingTrafficShell) 
+to configure Traffic Server.
+
+##### To view or change configuration options in Traffic Line:  ##### {#viewchangeconfigurationoptionsinTrafficLine}
+
+1. Log on to a Traffic Server node as the Traffic Server administrator and navigate to the Traffic Server `bin` directory. 
+2. To view a configuration setting, enter the following command:   
+`traffic_line -r _var_`  
+ where _`var`_ is the variable associated with the configuration option. For a list of variables, refer to [Configuration Variables](files.htm#config_var).
+3. To change the value of a configuration setting, enter the following command:   
+`traffic_line -s _var_ -v _value_`   
+ where _`var`_ is the variable associated with the configuration option and _`value`_ is the value you want to use. For a list of the variables, see [Configuration Variables](files.htm#config_var).  
+  
+ If the Traffic Server `bin` directory is not in your path, then prepend the Traffic Line command with `./` (for example, `./traffic_line -r variable`).
+
+## Configure Traffic Server Using Configuration Files ## {#ConfigureTSUsingConfigurationFiles}
+
+As an alternative to using Traffic Line or Traffic Shell, you can change Traffic 
+Server configuration options by manually editing specific variables in the 
+`records.config` file located in the Traffic Server `config` directory. To 
+edit the variables, open the file in a text editor (such as `vi` or `emacs`) 
+and change variable values. After you modify the `records.config` file, Traffic 
+Server must reread the configuration files. From the Traffic Server `bin` directory, 
+enter the Traffic Line command `traffic_line -x`. You may need to restart Traffic 
+Server to apply the configuration changes. 
+
+The following is a sample portion of the `records.config` file: 
+
+![](images/records.jpg)
+
+> 
+>   
+> 
+> _**Sample records.config file **_
+> 
+
+In addition to the `records.config` file, Traffic Server provides other configuration 
+files that are used to configure specific features. All configuration files 
+you can manually edit are described in [Configuration Files](files.htm). 
+
+         
+
+      
+
+   
+
+   
+
+         
+
+* [Overview](intro.htm)
+* [Getting Started](getstart.htm)
+* [HTTP Proxy Caching ](http.htm)
+* [Explicit Proxy Caching](explicit.htm)
+* [Reverse Proxy and HTTP Redirects](reverse.htm)
+* [Hierarchical Caching](hier.htm)
+* [Configuring the Cache](cache.htm)
+* [Monitoring Traffic](monitor.htm)
+* [Configuring Traffic Server](configure.htm)
+* [Security Options](secure.htm)
+* [Working with Log Files](log.htm)
+* [Traffic Line Commands](cli.htm)
+* [Event Logging Formats](logfmts.htm)
+* [Configuration Files](files.htm) 
+* [Traffic Server Error Messages](errors.htm)
+* [FAQ and Troubleshooting Tips](trouble.htm)
+* [Traffic Server 管理员指南](ts_admin_chinese.pdf) (PDF)
+
+   
+
+   
+
+ Copyright © 2011 [The Apache Software Foundation](http://www.apache.org/). 
+Licensed under the [Apache License](http://www.apache.org/licenses/), Version 
+2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the 
+Apache feather logo are trademarks of The Apache Software Foundation.
+
+
+

Added: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext?rev=1070302&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/event-logging-formats/index.en.mdtext Sun Feb 13 21:38:37 2011
@@ -0,0 +1,1038 @@
+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
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+
+   
+
+    
+      
+    
+
+ [![](/images/ts75.png)](/index.html)™
+      
+
+# Administrator's Guide # {#AdministratorsGuide}
+
+    
+
+   
+
+   
+
+      
+
+         
+
+            
+
+  
+
+# Appendix D - Event Logging Formats   # {#AppendixD-EventLoggingFormats}
+
+     
+
+ This appendix contains the following sections: 
+
+* [Custom Logging Fields](#66912) provides descriptions of logging fields.
+* [Logging Format Cross-Reference](#63460) provides cross-references between Trafic Server logging fields and Netscape & Squid logging fields (including Netscape Extended and Extended-2 fields).
+
+##       Custom Logging Fields      ## {#CustomLoggingFields}
+
+     
+
+ The following table describes Traffic Server custom logging fields. 
+
+     ** 
+
+ %<field symbol>
+
+** ** 
+
+ Description
+
+** 
+
+` {HTTP header field name}cqh`
+
+:   
+    
+     Logs the information in the requested field of the client request HTTP header. 
+    For example, ` %<{Accept-Language}cqh>` logs the `Accept-Language: `field in 
+    client request headers. 
+    
+    
+
+` {HTTP header field name}pqh`
+
+:   
+    
+     Logs the information in the requested field of the proxy request HTTP header. 
+    For example, ` %<{Authorization}pqh>` logs the` Authorization:` field in proxy 
+    request headers. 
+    
+    
+
+` {HTTP header field name}psh`
+
+:   
+    
+     Logs the information in the requested field of the proxy response HTTP header. 
+    For example, ` %<{Retry-After}psh>` logs the `Retry-After:` field in proxy 
+    response headers. 
+    
+    
+
+` {HTTP header field name}ssh`
+
+:   
+    
+     Logs the information in the requested field of the server response HTTP header. 
+    For example, ` %<{Age}ssh>` logs the `Age:` field in server response headers. 
+     
+    
+    
+
+` caun`
+
+:   
+    
+     The client authenticated username; result of the RFC931/ident lookup of the 
+    client username.
+    
+    
+
+` cfsc`
+
+:   
+    
+     The client finish status code; specifies whether the client request to Traffic 
+    Server was successfully completed (`FIN`) or interrupted (`INTR`).
+    
+    
+
+` chi`
+
+:   
+    
+     The IP address of the client's host machine.
+    
+    
+
+` cqbl`
+
+:   
+    
+     The client request transfer length; the body length in the client request 
+    to Traffic Server (in bytes).
+    
+    
+
+` cqhl`
+
+:   
+    
+     The client request header length; the header length in the client request 
+    to Traffic Server.
+    
+    
+
+` cqhm`
+
+:   
+    
+     The HTTP method in the client request to Traffic Server: `GET`, `POST`, and 
+    so on (subset of `cqtx`).
+    
+    
+
+` cqhv`
+
+:   
+    
+     The client request HTTP version.
+    
+    
+
+` cqtd`
+
+:   
+    
+     The client request timestamp. Specifies the date of the client request in 
+    the format yyyy-mm-dd, where yyyy is the 4-digit year, mm is the 2-digit month, 
+    and dd is the 2-digit day.
+    
+    
+
+` cqtn`
+
+:   
+    
+     The client request timestamp; date and time of the client's request (in the 
+    Netscape timestamp format).
+    
+    
+
+` cqtq`
+
+:   
+    
+     The client request timestamp, with millisecond resolution.
+    
+    
+
+` cqts`
+
+:   
+    
+     The client-request timestamp in Squid format; the time of the client request 
+    since January 1, 1970 UTC. Time is expressed in seconds, with millisecond resolution. 
+    
+    
+    
+
+` cqtt`
+
+:   
+    
+     The client request timestamp. The time of the client request in the format 
+    hh:mm:ss, where hh is the two-digit hour in 24-hour format, mm is the two-digit 
+    minutes value, and ss is the 2-digit seconds value (for example, 16:01:19). 
+    
+    
+    
+
+` cqtx`
+
+:   
+    
+     The full HTTP client request text, minus headers; for example, 
+    
+    
+                 
+    
+     ` GET http://www.company.com HTTP/1.0` 
+    
+    
+               
+    
+     In reverse proxy mode, Traffic Server logs the rewritten/mapped URL (according 
+    to the rules in the ` remap.config` file), and _ not_ the pristine/unmapped 
+    URL. To configure Traffic Server to log the original, unmapped URL, set the 
+    variable ` _proxy.config.url_remap.pristine_host_hdr _` in the ` records.config` 
+    file to ` 1` .
+    
+    
+
+` cqu`
+
+:   
+    
+     The universal resource identifier (URI) of the request from client to Traffic 
+    Server (subset of ` cqtx` ).
+    
+    
+                 
+    
+     In reverse proxy mode, Traffic Server logs the rewritten/mapped URL (according 
+    to the rules in the ` remap.config` file), and _ not _ the pristine/unmapped 
+    URL. To configure Traffic Server to log the original, unmapped URL, set the 
+    variable ` _proxy.config.url_remap.pristine_host_hdr _` in the ` records.config` 
+    file to ` 1` .
+    
+    
+
+` cquc`
+
+:   
+    
+     The client request canonical URL. This differs from `cqu` in that blanks (and 
+    other characters that might not be parsed by log analysis tools) are replaced 
+    by escape sequences. The escape sequence is a percentage sign followed by the 
+    ASCII code number in hex.
+    
+    
+                 
+    
+     In reverse proxy mode, Traffic Server logs the rewritten/mapped URL (according 
+    to the rules in the ` remap.config` file), and_ not _ the pristine/unmapped 
+    URL. To configure Traffic Server to log the original (unmapped) URL, set the 
+    ` _proxy.config.url_remap.pristine_host_hdr _` variable in the ` records.config` 
+    file to ` 1` .
+    
+    
+
+` cqup`
+
+:   
+    
+     The client request URL path; specifies the argument portion of the URL (everything after the host).   
+     For example, if the URL is ` http://www.company.com/images/x.gif` , then this field displays ` /images/x.gif`
+    
+    
+
+` cqus`
+
+:   
+    
+     The client request URL scheme.
+    
+    
+
+` cquuc`
+
+:   
+    
+     The client request unmapped URL canonical. This field records a URL before 
+    it is remapped (reverse proxy mode).
+    
+    
+
+` crc`
+
+:   
+    
+     The cache result code; specifies how the cache responded to the request (`HIT`, 
+    `MISS`, and so on).
+    
+    
+
+` fsiz`
+
+:   
+    
+     The size of the file (_n _ bytes) as seen by the origin server. 
+    
+    
+
+` pfsc`
+
+:   
+    
+     The proxy finish status code; specifies whether the Traffic Server request 
+    to the origin server was successfully completed (`FIN`) or interrupted (`INTR`). 
+    
+    
+    
+
+` phn`
+
+:   
+    
+     The hostname of the Traffic Server that generated the log entry in collated 
+    log files.
+    
+    
+
+` phr`
+
+:   
+    
+     The proxy hierarchy route; the route Traffic Server used to retrieve the object. 
+    
+    
+    
+
+` pqbl`
+
+:   
+    
+     The proxy request transfer length; the body length in Traffic Server's request 
+    to the origin server.
+    
+    
+
+` pqhl`
+
+:   
+    
+     The proxy request header length; the header length in Traffic Server's request 
+    to the origin server.
+    
+    
+
+` pqsi`
+
+:   
+    
+     The proxy request server IP address (0 on cache hits and parent-ip for requests 
+    to parent proxies).
+    
+    
+
+` pqsn`
+
+:   
+    
+     The proxy request server name; the name of the server that fulfilled the request. 
+     
+    
+    
+
+` prcb`
+
+:   
+    
+     The number of proxy response bytes to the client from the cache.
+    
+    
+
+` prob`
+
+:   
+    
+     The number of proxy response bytes to the client from the origin server.
+    
+    
+
+` pscl`
+
+:   
+    
+     The length of the Traffic Server response to the client (in bytes).
+    
+    
+
+` psct`
+
+:   
+    
+     The content type of the document from server response header: (for example, 
+    ` img` /` gif` ).
+    
+    
+
+` pshl`
+
+:   
+    
+     The header length in Traffic Server's response to the client.
+    
+    
+
+` psql`
+
+:   
+    
+     The proxy response transfer length in Squid format (includes header and content 
+    length).
+    
+    
+
+` pssc`
+
+:   
+    
+     The HTTP response status code from Traffic Server to the client.
+    
+    
+
+` shi`
+
+:   
+    
+     The IP address resolved from the DNS name lookup of the host in the request. For hosts with multiple IP addresses, this field records the IP address resolved from that particular DNS lookup.   
+     This can be misleading for cached documents. For example: if the first request was a cache miss and came from` **IP1**` for server `**S**` and the second request for server `**S**` resolved to `**IP2**` but came from the cache, then the log entry for the second request will show **`IP2`**.
+    
+    
+
+` shn`
+
+:   
+    
+     The hostname of the origin server.
+    
+    
+
+` sscl`
+
+:   
+    
+     The response length (in bytes) from origin server to Traffic Server.
+    
+    
+
+` sshl `
+
+:   
+    
+     The header length in the origin server response to Traffic Server (in bytes). 
+    
+    
+    
+
+` sshv`
+
+:   
+    
+     The server response HTTP version (1.0, 1.1, etc.).
+    
+    
+
+` sssc`
+
+:   
+    
+     The HTTP response status code from origin server to Traffic Server.
+    
+    
+
+` ttms`
+
+:   
+    
+     The time Traffic Server spends processing the client request; the number of 
+    milliseconds between the time the client establishes the connection with Traffic 
+    Server and the time Traffic Server sends the last byte of the response back 
+    to the client.
+    
+    
+
+` ttmsf`
+
+:   
+    
+     The time Traffic Server spends processing the client request as a fractional number of seconds. Time is specified in millisecond resolution; however, instead of formatting the output as an integer (as with `ttms`), the display is formatted as a floating-point number representing a fractional number of seconds.  
+     For example: if the time is 1500 milliseconds, then this field displays 1.5 while the `ttms` field displays 1500 and the `tts` field displays 1.
+    
+    
+
+` tts`
+
+:   
+    
+     The time Traffic Server spends processing the client request; the number of 
+    seconds between the time at which the client establishes the connection with 
+    Traffic Server and the time at which Traffic Server sends the last byte of 
+    the response back to the client.
+    
+    
+
+## Logging Format Cross-Reference  ## {#LoggingFormatCross-Reference}
+
+  
+
+ The following sections illustrate the correspondence between Traffic Server 
+logging fields and standard logging fields for the Squid and Netscape formats. 
+ 
+
+     
+
+###         Squid Logging Formats      ### {#SquidLoggingFormats}
+
+  
+
+ The following table lists the Squid logging fields and the corresponding logging 
+field symbols. 
+
+  ** 
+
+ Squid
+
+** ** 
+
+ Field Symbols
+
+** 
+
+` time`
+
+:   
+    
+    ` cqts`
+    
+    
+
+` elapsed`
+
+:   
+    
+    ` ttms`
+    
+    
+
+` client`
+
+:   
+    
+    ` chi`
+    
+    
+
+` action/code `
+
+:   
+    
+    ` crc/pssc`
+    
+    
+
+` size`
+
+:   
+    
+    ` psql`
+    
+    
+
+` method`
+
+:   
+    
+    ` cqhm`
+    
+    
+
+` url`
+
+:   
+    
+    ` cquc`
+    
+    
+
+` ident`
+
+:   
+    
+    ` caun`
+    
+    
+
+` hierarchy/from`
+
+:   
+    
+    ` phr/pqsn`
+    
+    
+
+` content`
+
+:   
+    
+    ` psct`
+    
+    
+
+###         Netscape Common Logging Formats       ### {#NetscapeCommonLoggingFormats}
+
+  
+
+ The following table lists the Netscape Common logging fields and the corresponding 
+Traffic Server logging field symbols. 
+
+      ** 
+
+ Netscape Common
+
+** ** 
+
+ Field Symbols
+
+** 
+
+` host`
+
+:   
+    
+    ` chi`
+    
+    
+
+` usr`
+
+:   
+    
+    ` caun`
+    
+    
+
+` [time]`
+
+:   
+    
+    ` [cqtn]`
+    
+    
+
+ `"req"`
+
+:   
+    
+     `"cqtx"`
+    
+    
+
+` s1`
+
+:   
+    
+    ` pssc`
+    
+    
+
+` c1`
+
+:   
+    
+    ` pscl`
+    
+    
+
+###         Netscape Extended Logging Formats       ### {#NetscapeExtendedLoggingFormats}
+
+  
+
+ The following table lists the Netscape Extended logging fields and the corresponding 
+Traffic Server logging field symbols. 
+
+      ** 
+
+ Netscape Extended
+
+** ** 
+
+ Field Symbols 
+
+** 
+
+` host`
+
+:   
+    
+    ` chi`
+    
+    
+
+` usr`
+
+:   
+    
+    ` caun`
+    
+    
+
+` [time]`
+
+:   
+    
+    ` [cqtn]`
+    
+    
+
+ `"req"`
+
+:   
+    
+     `"cqtx"`
+    
+    
+
+` s1`
+
+:   
+    
+    ` pssc`
+    
+    
+
+` c1`
+
+:   
+    
+    ` pscl`
+    
+    
+
+` s2`
+
+:   
+    
+    ` sssc`
+    
+    
+
+` c2`
+
+:   
+    
+    ` sscl`
+    
+    
+
+` b1`
+
+:   
+    
+    ` cqbl`
+    
+    
+
+` b2`
+
+:   
+    
+    ` pqbl`
+    
+    
+
+` h1`
+
+:   
+    
+    ` cqhl`
+    
+    
+
+` h2`
+
+:   
+    
+    ` pshl`
+    
+    
+
+` h3`
+
+:   
+    
+    ` pqhl`
+    
+    
+
+` h4`
+
+:   
+    
+    ` sshl`
+    
+    
+
+` xt`
+
+:   
+    
+    ` tts`
+    
+    
+
+###         Netscape Extended-2 Logging Formats       ### {#NetscapeExtended-2LoggingFormats}
+
+  
+
+ The following table lists the Netscape Extended-2 logging fields and the corresponding 
+Traffic Server logging field symbols.
+
+  ** 
+
+ Netscape Extended-2
+
+** ** 
+
+ Field Symbols
+
+** 
+
+` host`
+
+:   
+    
+    ` chi`
+    
+    
+
+` usr`
+
+:   
+    
+    ` caun`
+    
+    
+
+` [time]`
+
+:   
+    
+    ` [cqtn]`
+    
+    
+
+ `"req"`
+
+:   
+    
+     `"cqtx"`
+    
+    
+
+` s1`
+
+:   
+    
+    ` pssc`
+    
+    
+
+` c1`
+
+:   
+    
+    ` pscl`
+    
+    
+
+` s2`
+
+:   
+    
+    ` sssc`
+    
+    
+
+` c2`
+
+:   
+    
+    ` sscl`
+    
+    
+
+` b1`
+
+:   
+    
+    ` cqbl`
+    
+    
+
+` b2`
+
+:   
+    
+    ` pqbl`
+    
+    
+
+` h1`
+
+:   
+    
+    ` cqhl`
+    
+    
+
+` h2`
+
+:   
+    
+    ` pshl`
+    
+    
+
+` h3`
+
+:   
+    
+    ` pqhl`
+    
+    
+
+` h4`
+
+:   
+    
+    ` sshl`
+    
+    
+
+` xt`
+
+:   
+    
+    ` tts`
+    
+    
+
+` route`
+
+:   
+    
+    ` phr`
+    
+    
+
+` pfs`
+
+:   
+    
+    ` cfsc`
+    
+    
+
+` ss`
+
+:   
+    
+    ` pfsc`
+    
+    
+
+` crc`
+
+:   
+    
+    ` crc`
+    
+    
+
+      
+
+   
+
+   
+
+         
+
+* [Overview](intro.htm)
+* [Getting Started](getstart.htm)
+* [HTTP Proxy Caching ](http.htm)
+* [Explicit Proxy Caching](explicit.htm)
+* [Reverse Proxy and HTTP Redirects](reverse.htm)
+* [Hierarchical Caching](hier.htm)
+* [Configuring the Cache](cache.htm)
+* [Monitoring Traffic](monitor.htm)
+* [Configuring Traffic Server](configure.htm)
+* [Security Options](secure.htm)
+* [Working with Log Files](log.htm)
+* [Traffic Line Commands](cli.htm)
+* [Event Logging Formats](logfmts.htm)
+* [Configuration Files](files.htm) 
+* [Traffic Server Error Messages](errors.htm)
+* [FAQ and Troubleshooting Tips](trouble.htm)
+* [Traffic Server 管理员指南](ts_admin_chinese.pdf) (PDF)
+
+   
+
+   
+
+ Copyright © 2011 [The Apache Software Foundation](http://www.apache.org/). 
+Licensed under the [Apache License](http://www.apache.org/licenses/), Version 
+2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the 
+Apache feather logo are trademarks of The Apache Software Foundation.
+
+
+

Added: 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=1070302&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/explicit-proxy-caching/index.en.mdtext Sun Feb 13 21:38:37 2011
@@ -0,0 +1,169 @@
+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
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+
+   
+
+    
+      
+    
+
+ [![](/images/ts75.png)](/index.html)™
+      
+
+# Administrator's Guide # {#AdministratorsGuide}
+
+    
+
+   
+
+   
+
+      
+
+         
+
+            
+
+# 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 
+web browsers to send HTTP requests to the Traffic Server proxy cache by configuring 
+their browsers to download proxy configuration instructions from a [PAC file](#UsingPACFile) 
+(Proxy Auto-Configuration file).
+
+### Configuring Browsers Manually  ### {#ConfiguringBrowsersManually}
+
+To manually configure a browser to send HTTP requests to Traffic Server, clients 
+must provide the following information: 
+
+* The fully-qualified hostname or IP address of the Traffic Server node
+* The Traffic Server proxy server port (port 8080)
+
+In addition, clients can specify _not_ to use Traffic Server for certain sites 
+- in such cases, requests to the listed sites go directly to the origin server. 
+The procedures for manual configuration vary among browser versions; refer 
+to specific browser documentation for complete proxy configuration instructions. 
+You do not need to set any special configuration options on Traffic Server 
+if you want to accept requests from manually-configured browsers. 
+
+### Using a PAC File  ### {#UsingaPACFile}
+
+A **PAC file** is a specialized JavaScript function definition that a browser 
+calls to determine how requests are handled. Clients must specify (in their 
+browser settings) the URL from which the PAC file is loaded. You can store 
+a PAC file on Traffic Server (or on any server in your network) and then provide 
+the URL for this file to your clients. 
+
+If you want to store a PAC file on the Traffic Server system, then you must 
+perform the following configuration: 
+
+* Either copy an existing PAC file into the Traffic Server `config` directory or enter a script that defines the proxy server configuration settings in the `proxy.pac` file provided (the file is empty by default). 
+* Specify the port Traffic Server uses to serve the PAC file. The default port is 8083.
+
+##### Configure Traffic Server to provide a PAC file manually:  ##### {#ConfigureTSprovideaPACfilemanually}
+
+1. If you have an existing PAC file, then replace the `proxy.pac` file located in the Traffic Server `config` directory with the existing file. 
+2. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+3. Edit the following variable:
+4. **Variable** **Description** 
+`_proxy.config.admin.autoconf_port_`
+:   
+		
+		Set this variable to specify the port Traffic Server uses to serve the PAC 
+		file. The default port is 8083.
+		
+				  
+
+5. Save and close the `records.config` file. 
+6. In a text editor, open the `proxy.pac` file located in the Traffic Server `config` directory. 
+
+* If you copied an existing PAC file into the Traffic Server config directory, then the `proxy.pac` file contains your proxy configuration settings. Check the settings and make changes if necessary. 
+* If you did not copy an existing PAC file into the Traffic Server `config` directory, then the `proxy.pac` file is empty. Enter a script that will provide the proxy server configuration settings. A sample script is provided in [Sample PAC File](#SamplePACFile). 
+
+Save and close the `proxy.pac` file. 
+  Restart Traffic Server. 
+  Inform your users to set their browsers to point to this PAC file; [click here 
+for browser settings](#SetBrowsersPointPACFile). 
+
+#### 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. 
+All other requests go to the Traffic Server named `myproxy.company.com`.
+
+`function FindProxyForURL(url, host)   
+{  
+ if (isPlainHostName(host)) ||  
+ (localHostOrDomainIs(host, ".company.com")) {  
+ return "DIRECT";  
+ }  
+ else  
+ return "PROXY myproxy.company.com:8080;" +  
+ "DIRECT";   
+} `
+
+###   ### {# }
+
+ 
+
+         
+
+      
+
+   
+
+   
+
+         
+
+* [Overview](intro.htm)
+* [Getting Started](getstart.htm)
+* [HTTP Proxy Caching ](http.htm)
+* [Explicit Proxy Caching](explicit.htm)
+* [Reverse Proxy and HTTP Redirects](reverse.htm)
+* [Hierarchical Caching](hier.htm)
+* [Configuring the Cache](cache.htm)
+* [Monitoring Traffic](monitor.htm)
+* [Configuring Traffic Server](configure.htm)
+* [Security Options](secure.htm)
+* [Working with Log Files](log.htm)
+* [Traffic Line Commands](cli.htm)
+* [Event Logging Formats](logfmts.htm)
+* [Configuration Files](files.htm) 
+* [Traffic Server Error Messages](errors.htm)
+* [FAQ and Troubleshooting Tips](trouble.htm)
+* [Traffic Server 管理员指南](ts_admin_chinese.pdf) (PDF)
+
+   
+
+   
+
+ Copyright © 2011 [The Apache Software Foundation](http://www.apache.org/). 
+Licensed under the [Apache License](http://www.apache.org/licenses/), Version 
+2.0. Apache Traffic Server, Apache, the Apache Traffic Server logo, and the 
+Apache feather logo are trademarks of The Apache Software Foundation.
+
+
+



Mime
View raw message