trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1089484 - /trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext
Date Wed, 06 Apr 2011 15:11:04 GMT
Author: igalic
Date: Wed Apr  6 15:11:04 2011
New Revision: 1089484

URL: http://svn.apache.org/viewvc?rev=1089484&view=rev
Log:
Fixing markup and links

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuring-cache/index.en.mdtext

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=1089484&r1=1089483&r2=1089484&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
Wed Apr  6 15:11:04 2011
@@ -19,12 +19,12 @@ Notice:    Licensed to the Apache Softwa
 # 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 
+**object store** that indexes objects according to URLs and their associated 
 headers.
 
 This chapter discusses the following topics: 
 
-* [The Traffic Server Cache](#TrafficEdgeCache)
+* [The Traffic Server Cache](#TSCache)
 * [The RAM Cache](#RAMCache)
 * [Changing the Size of the RAM Cache](#ChangingSizeRAMCache)
 * [Changing Cache Capacity](#ChangingCacheCapacity)
@@ -85,15 +85,9 @@ 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)).

+3. Set the variable [_`proxy.config.cache.ram_cache.size`_](../configuration-files/records.config#proxy.config.cache.ram_cache.size)
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.
+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](../getting-started#StartingTS)).
 
  
 
@@ -110,7 +104,7 @@ disks or to add new disks to a Traffic S
 
 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)).
+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](../configuration-files/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. 
 
@@ -121,7 +115,7 @@ disk or to remove disks from a Traffic S
 
 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)). 
+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](../configuration-files/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. 
 
@@ -146,7 +140,7 @@ the **http** partition type for HTTP obj
 ##### 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)).

+2. Enter a line in the file for each partition you want to create (refer to [partition.config](../configuration-files/partition.config)).

 3. Save and close the `partition.config` file. 
 4. Restart Traffic Server. 
 
@@ -176,7 +170,7 @@ are not listed. This generic partition i
 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 
+**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. 
@@ -186,8 +180,8 @@ assignment during periods of low traffic
 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)). 
+4. Enter a line in the file to allocate the partition(s) used for each origin server and/or
domain (refer to [hosting.config](../configuration-files/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](../configuration-files/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. 
@@ -198,15 +192,8 @@ By default, Traffic Server allows object
 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. 
+1. Set [_`proxy.config.cache.max_doc_size`_](../configuration-files/records.config#proxy.config.cache.max_doc_size)
to specify the maximum size allowed for objects in the cache in bytes.
+   `0` (zero) if you do not want a size limit.
 5. Run the command `traffic_line -x` to apply the configuration changes. 
 
 ## Clearing the Cache ## {#ClearingCache}
@@ -218,11 +205,11 @@ when Traffic Server is running. 
 
 ##### To clear the cache:  ##### {#clearcache}
 
-1. Stop Traffic Server (refer to [Stopping Traffic Server](getstart.htm#StoppingTrafficEdge)).

+1. Stop Traffic Server (refer to [Stopping Traffic Server](../getting-started#StoppingTS)).
 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)).
+3. Restart Traffic Server (refer to [Starting Traffic Server](../getting-started#StoppingTS)).
 
 ## Removing an Object From the Cache ## {#RemovinganObjectFromCache}
 
@@ -234,15 +221,19 @@ a `404 File Not Found` message is return
 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
+      $ 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 
@@ -259,7 +250,7 @@ delete, and invalidate URLs in the cache
 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).

+file, see [Controlling Host Access to Traffic Manager](../security-options#ControllingHostAccessTrafficManager).
  
 
 ### Accessing the Cache Inspector Utility  ### {#AccessingCacheInspectorUtility}
@@ -267,15 +258,12 @@ file, see [Controlling Host Access to Tr
 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}`
+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://yourhost/myCI`
 6. The Cache page opens (see [Using the Cache Page](#UsingCachePage) below).
 
 ### Using the Cache Page  ### {#UsingCachePage}
@@ -285,54 +273,15 @@ 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. 
+* 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.
-
-
-



Mime
View raw message