trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1070302 [4/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
Added: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext?rev=1070302&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/security-options/index.en.mdtext Sun Feb 13 21:38:37 2011
@@ -0,0 +1,427 @@
+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}
+
+    
+
+   
+
+   
+
+      
+
+         
+
+            
+
+# Security Options # {#SecurityOptions}
+
+Traffic Server provides a number of security features.
+
+This chapter discusses the following topics: 
+
+* [Controlling Client Access to the Proxy Cache](#ControllingClientAccessProxyCache)
+* [Controlling Access: SSL](#ControllingAccessTrafficManager)
+* [Configuring DNS Server Selection (Split DNS)](#ConfiguringDNSServerSelectionSplit)
+* [Configuring Proxy Authentication](#ConfiguringProxyAuthentication)
+* [Using SSL Termination](#UsingSSLTermination)
+
+## Controlling Client Access to the Proxy Cache ## {#ControllingClientAccessProxyCache}
+
+You can configure Traffic Server to allow only certain clients to use the proxy 
+cache by editing a configuration file.
+
+##### To specify the clients allowed to use the proxy cache:  ##### {#specifyclientsalloweduseproxycache}
+
+1. In a text editor, open the `ip_allow.config` file located in the Traffic Server `config` directory. 
+2. Add a line in the file for each IP address or range of IP addresses allowed to access Traffic Server (refer to [ip_allow.config](files.htm#ip_allow.config)). 
+3. Save and close the `ip_allow.config` file. 
+4. Navigate to the Traffic Server `bin` directory.
+5. Run the command `traffic_line -x` to apply the configuration changes.
+
+## Controlling Access via SSL ## {#ControllingAccessviaSSL}
+
+By restricting access to Traffic Server, you ensure that only authenticated 
+users can change configuration options and view network traffic statistics. 
+ 
+
+### Using SSL for Secure Administration ### {#UsingSSLforSecureAdministration}
+
+Traffic Server supports the Secure Sockets Layer (**SSL**) protocol to provide 
+protection for remote administrative monitoring and configuration. SSL security 
+provides authentication for both ends of a network connection via certificates 
+and provides privacy via encryption. 
+
+To use SSL, you must do the following: 
+
+* Obtain an SSL certificate 
+* Enable SSL 
+
+#### Obtain an SSL Certificate  #### {#ObtainanSSLCertificate}
+
+The SSL certificate is a text file you must install in the Traffic Server `config` 
+directory. Either rename the certificate to the default filename `private_key.pem`, 
+or specify the name of the certificate in the configuration file (follow the 
+procedure in [Enabling SSL](#EnablingSSL)). 
+
+#### Enable SSL #### {#EnableSSL}
+
+After you've obtained an SSL certificate, enable SSL by manually editing a 
+configuration file. Follow the steps below:
+
+1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+2. Edit the following variables:
+3. **Variable** **Description** 
+`_proxy.config.admin.use_ssl_`
+:   Set this variable to `1` to enable SSL.
+`_proxy.config.admin.ssl_cert_file_`
+:   Set this variable to specify the filename of the SSL certificate. You have 
+		to change the filename only if the certificate file does not use the default 
+		name `private_key.pem`.
+
+4. Save and close the `records.config` file. 
+5. Navigate to the Traffic Server `bin` directory.
+6. Run the command `traffic_line -x` to apply the configuration changes.
+
+## Configuring DNS Server Selection (Split DNS) ## {#ConfiguringDNSServerSelection(SplitDNS)}
+
+The **Split DNS **option enables you to configure Traffic Server to use multiple 
+DNS servers, as dictated by your security requirements. For example, you might 
+configure Traffic Server to use one set of DNS servers to resolve hostnames 
+on your internal network, while allowing DNS servers outside the firewall to 
+resolve hosts on the Internet. This maintains the security of your intranet, 
+while continuing to provide direct access to sites outside your organization. 
+ 
+
+To configure Split DNS, you must do the following: 
+
+* Specify the rules for performing DNS server selection based on the destination domain, the destination host, or a URL regular expression. 
+* Enable the **Split DNS** option.
+
+##### To configure Split DNS:  ##### {#configureSplitDNS}
+
+1. In a text editor, open the `splitdns.config` file located in the Traffic Server `config` directory. 
+2. Add rules to the `splitdns.config` file. For information about the format of the `splitdns.config` file, [click here](files.htm#splitdns.config). 
+3. Save and close the `splitdns.config` file.
+4. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+5. Edit the following variables:
+6. **Variable** **Description** 
+`_proxy.process.dns.splitDNS.enabled_`
+:   Set this variable to `1` to enable split DNS.
+`_proxy.config.dns.splitdns.def_domain_`
+:   Set this variable to specify the default domain for split DNS requests. Traffic 
+		Server appends this value automatically to a hostname that does not include 
+		a domain before determining which DNS server to use.
+
+7. Save and close the `records.config` file. 
+8. Navigate to the Traffic Server `bin` directory. 
+9. Run the command `traffic_line -x` to apply the configuration changes. 
+
+## Using SSL Termination ## {#UsingSSLTermination}
+
+The Traffic Server **SSL termination** option enables you to secure connections 
+in reverse proxy mode between a client and a Traffic Server and/or Traffic 
+Server and an origin server. 
+
+The following sections describe how to enable and configure the SSL termination 
+option. 
+
+* Enable and configure SSL termination for client/Traffic Server connections: [Client and Traffic Server Connections](#ClientTrafficEdgeConnections). 
+* Enable and configure SSL termination for Traffic Server/origin server connections: [Traffic Server and Origin Server Connections](#TrafficEdgeOriginServerConnections). 
+* Enable and configure SSL termination for both client/Traffic Server and Traffic Server/origin server connections: [Client and Traffic Server Connections](#ClientTrafficEdgeConnections) and [Traffic Server and Origin Server Connections](#TrafficEdgeOriginServerConnections), respectively.
+
+If you install an SSL accelerator card on your Traffic Server system, then 
+you must perform additional configuration steps - refer to [Configuring Traffic 
+Server to Use an SSL Accelerator Card](#ConfiguringTrafficEdgeSSLAcceleratorCard). 
+ 
+
+### Client and Traffic Server Connections  ### {#ClientTSConnections}
+
+The figure below illustrates communication between a client and Traffic Server 
+(and between Traffic Server and an origin server) when the SSL termination 
+option is enabled & configured for** client/Traffic Server connections only**. 
+
+![](images/ssl_c.jpg)
+
+> 
+>   
+> 
+> _**Client and Traffic Server communication using SSL termination**_
+> 
+
+The figure above depicts the following: 
+
+**Step 1:** The client sends an HTTPS request for content. Traffic Server receives 
+the request and performs the SSL 'handshake' to authenticate the client (depending 
+on the authentication options configured) and determine the encryption method 
+that will be used. If the client is allowed access, then Traffic Server checks 
+its cache for the requested content. 
+
+**Step 2:** If the request is a cache hit and the content is fresh, thenTraffic 
+Server encrypts the content and sends it to the client. The client decrypts 
+the content (using the method determined during the handshake) and displays 
+it. 
+
+**Step 3:** If the request is a cache miss or cached content is stale, then 
+Traffic Server communicates with the origin server via HTTP and obtains a plain 
+text version of the content. Traffic Server saves the plain text version of 
+the content in its cache, encrypts the content, and sends it to the client. 
+The client decrypts and displays the content. 
+
+To configure Traffic Server to use the SSL termination option for client/Traffic 
+Server connections, you must do the following: 
+
+* Obtain and install an SSL server certificate from a recognized certificate authority (such as VeriSign). The SSL server certificate contains information that enables the client to authenticate Traffic Server and exchange encryption keys. 
+* Configure SSL termination options: 
+* Enable the **SSL termination** option. 
+  Set the port number used for SSL communication. 
+  Specify the filename and location of the server certificate. 
+  (Optional) Configure the use of client certificates.   
+ Client certificates are located on the client. If you configure Traffic Server to require client certificates, then Traffic Server verifies the client certificate during the SSL handshake that authenticates the client. If you configure Traffic Server to _not_ require client certificates, then access to Traffic Server is managed through other Traffic Server options that have been set (such as rules in the `ip_allow.config` file). 
+  Specify the filename and location of the Traffic Server private key (if the private key is not located in the server certificate file).   
+ Traffic Server uses its private key during the SSL handshake to decrypt the session encryption keys. The private key must be stored and protected against theft. 
+  (Optional) Configure the use of Certification Authorities (CAs).   
+ CAs add security by verifying the identity of the person requesting a certificate.
+
+##### To configure SSL termination for client/Traffic Server connections:  ##### {#configureSSLterminationforclient/TSconnections}
+
+1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+2. Edit the following variables in the `SSL Termination` section of the file: 
+3. **Variable** **Description** 
+`_proxy.config.ssl.enabled_`
+:   Set this variable to 1 to enable the SSL termination option.
+`_proxy.config.ssl.server_port_`
+:   Set this variable to specify the port used for SSL communication. The default 
+		port is 443.
+`_proxy.config.ssl.client.certification_level_`
+:   Set this variable to one of the following values:  
+		`0` - no client certificates are required. Traffic Server does not verify client certificates during the SSL handshake. Access to Traffic Server depends on Traffic Server configuration options (such as access control lists).  
+		`1` - client certificates are optional. If a client has a certificate, then the certificate is validated. If the client does not have a certificate, then the client is still allowed access to Traffic Server unless access is denied through other Traffic Server configuration options.  
+		`2` - client certificates are required. The client must be authenticated during the SSL handshake; Clients without a certificate are not allowed to access Traffic Server.
+`_proxy.config.ssl.server.cert.filename_`
+:   Set this variable to specify the filename of the Traffic Server SSL server certificate.  
+		 Traffic Server provides a demo server certificate called `server.pem` - use this certificate to verify that the SSL feature is working.  
+		 If you are using multiple server certificates, then set this variable to specify the default filename.
+`_proxy.config.ssl.server.cert.path_`
+:   Set this variable to specify the location of the Traffic Server SSL server 
+		certificate. The default directory is the Traffic Server `config` directory. 
+		
+`_proxy.config.ssl.server.private_key.filename_`
+:   Set this variable to specify the filename of the Traffic Server private key. 
+		Change this variable only if the private key is not located in the Traffic 
+		Server SSL server certificate file.
+`_proxy.config.ssl.server.private_key.path_`
+:   Set this variable to specify the location of the Traffic Server private key. 
+		Change this variable only if the private key is not located in the Traffic 
+		Server SSL server certificate file.
+`_proxy.config.ssl.CA.cert.filename_`
+:   Specify the filename of the certificate authority that client certificates 
+		will be verified against. The default value is `NULL`.
+`_proxy.config.ssl.CA.cert.path_`
+:   Specify the location of the certificate authority file that client certificates 
+		will be verified against. The default value is `NULL`.
+
+4. Save and close the `records.config` file. 
+5. Navigate to the Traffic Server `bin` directory. 
+6. Run the command `traffic_line -L` to restart Traffic Server on the local node or `traffic_line -M` to restart Traffic Server on all the nodes in a cluster. 
+
+### Traffic Server and Origin Server Connections ### {#TSOriginServerConnections}
+
+The figure below illustrates communication between Traffic Server and an origin 
+server when the SSL termination option is enabled for **Traffic Server/origin 
+server connections**.
+
+![](images/ssl_os.jpg)
+
+> 
+>   
+> 
+> _**Traffic Server and origin server communication using SSL termination**_ 
+> 
+
+The figure above depicts the following: 
+
+**Step 1:** If a client request is a cache miss or is stale, then Traffic Server 
+sends an HTTPS request for the content to the origin server. The origin server 
+receives the request and performs the SSL handshake to authenticate Traffic 
+Server and determine the encryption method to be used. 
+
+**Step 2:** If Traffic Server is allowed access, then the origin server encrypts 
+the content and sends it to Traffic Server, where it is decrypted (using the 
+method determined during the handshake). A plain text version of the content 
+is saved in the cache. 
+
+**Step 3:** If SSL termination is enabled for client /Traffic Server connections, 
+then Traffic Server re-encrypts the content and sends it to the client via 
+HTTPS, where it is decrypted and displayed. If SSL termination is not enabled 
+for client/Traffic Server connections, then Traffic Server sends the plain 
+text version of the content to the client via HTTP. 
+
+To configure Traffic Server to use the SSL termination option for Traffic Server 
+and origin server connections, you must do the following: 
+
+* Obtain and install an SSL client certificate from a recognized certificate authority (such as VeriSign). The SSL client certificate contains information that allows the origin server to authenticate Traffic Server (the client certificate is optional). 
+* Configure SSL termination options: 
+* Enable the SSL termination option. 
+   Set the port number used for SSL communication. 
+   Specify the filename and location of the SSL client certificate (if you choose 
+to use a client certificate). 
+   Specify the filename and location of the Traffic Server private key (if the private key is not located in the client certificate file).   
+ Traffic Server uses its private key during the SSL handshake to decrypt the session encryption keys. The private key must be stored and protected against theft. 
+   Configure the use of CAs.   
+ CAs allow the Traffic Server that's acting as a client to verify the identity of the server with which it is communicating, thereby enabling exchange of encryption keys.
+ 
+
+##### To configure SSL termination for Traffic Server/origin server connections:  ##### {#configureSSLterminationforTS/originserverconnections}
+
+1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+2. Edit the following variables in the `SSL Termination `section of the file: 
+3. **Variable** **Description** 
+`_proxy.config.ssl.auth.enabled_`
+:   Set this variable to `1` to enable the SSL termination option.
+`_proxy.config.ssl.server_port_`
+:   Set this variable to specify the port used for SSL communication. The default 
+		port is `443`.
+`_proxy.config.ssl.client.verify.server_`
+:   Set this option to `1` to require Traffic Server to verify the origin server 
+		certificate with the Certificate Authority.
+`_proxy.config.ssl.client.cert.filename_`
+:   If you have installed an SSL client certificate on Traffic Server, then set 
+		this variable to specify the client certificate filename.
+`_proxy.config.ssl.client.cert.path_`
+:   If you have installed an SSL client certificate on Traffic Server, then set 
+		this variable to the location of the client certificate. The default location 
+		is the Traffic Server `config` directory.
+`_proxy.config.ssl.client.private_key.filename_`
+:   Set this variable to specify the filename of the Traffic Server private key. 
+		Change this variable only if the private key is not located in the Traffic 
+		Server SSL client certificate file.
+`_proxy.config.ssl.client.private_key.path_`
+:   Set this variable to specify the location of the Traffic Server private key. 
+		Change this variable only if the private key is not located in the SSL client 
+		certificate file.
+`_proxy.config.ssl.client.CA.cert.filename_`
+:   Specify the filename of the Certificate Authority against which the origin 
+		server will be verified. The default value is `NULL`.
+`_proxy.config.ssl.client.CA.cert.path_`
+:   Specify the location of the Certificate Authority file against which the origin 
+		server will be verified. The default value is `NULL`.
+
+4. Save and close the `records.config` file. 
+5. Navigate to the Traffic Server `bin` directory. 
+6. Run the command `traffic_line -L` to restart Traffic Server on the local node or `traffic_line -M` to restart Traffic Server on all the nodes in a cluster. 
+
+### Configuring Traffic Server to Use an SSL Accelerator Card  ### {#ConfiguringTSUseanSSLAcceleratorCard}
+
+You can install an SSL accelerator card on your Traffic Server machine to accelerate 
+the number of requests Traffic Server can process. Traffic Server supports 
+the Cavium accelerator card. If you opt not to use an SSL accelerator card, 
+then you'll use your normal SSL library; if you install the Cavium card, then 
+you'll use the library supported & provided by the card manufacturer.
+
+##### Configure Traffic Server to use an SSL accelerator card:  ##### {#ConfigureTSuseanSSLacceleratorcard}
+
+1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory. 
+2. Edit the following variables in the `SSL Termination` section of the file: 
+3. **Variable** **Description** 
+`_proxy.confg.ssl.accelerator_required_`
+:   Set this specify if an accelerator card is required for operation. 
+		
+		You may specify:  
+		`0` - not required  
+		`1` - accelerator card is required and Traffic Server will not enable SSL unless an accelerator card is present.  
+		`2` - accelerator card is required and Traffic Server will not start unless an accelerator card is present.
+		
+		
+				  
+		
+		You can verify operation by running` /home/y/bin/openssl_accelerated` (this 
+		comes as part of `openssl_engines_init`).
+		
+		
+`_proxy.confg.ssl.accelerator.type_`
+:   
+		
+		Specifies if the Cavium SSL accelerator card is installed on (and required 
+		by) your Traffic Server machine:
+		
+		
+						
+		
+		`0` = none. No SSL accelerator card is installed on the Traffic Server machine, 
+		so the CPU on the Traffic Server machine determines the number of requests 
+		served per second.
+		
+		
+				  
+		
+		`1` = an accelerator card is present and required by Traffic Server.
+		
+		
+
+4. Save and close the `records.config` file. 
+5. Navigate to the Traffic Server `bin` directory. 
+6. Run the command `traffic_line -L` to restart Traffic Server on the local node or `traffic_line -M` to restart Traffic Server on all the nodes in a cluster. 
+
+      
+
+   
+
+   
+
+         
+
+* [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/traffic-line-commands/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext?rev=1070302&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-line-commands/index.en.mdtext Sun Feb 13 21:38:37 2011
@@ -0,0 +1,885 @@
+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 C - Traffic Line Commands       # {#AppendixC-TrafficLineCommands}
+
+  
+
+ This appendix contains the following sections: 
+
+* [Traffic Line Commands](#1053987)
+* [Traffic Line Variables](#1025718)
+
+##         Traffic Line Commands      ## {#TrafficLineCommands}
+
+     
+
+ Use Traffic Line to execute individual Traffic Server commands and to script 
+multiple commands in a shell. Execute Traffic Line commands from the Traffic 
+Server `bin` directory. If the Traffic Server `bin` directory is not in your 
+path, then prepend the Traffic Line command with `./` (for example: `./traffic_line 
+-p`). 
+
+  
+
+ The following table describes all the commands available in Traffic Line. 
+ 
+
+      ** 
+
+ Command
+
+** ** 
+
+ Description
+
+** 
+
+ ` traffic_line -b` 
+
+:   
+    
+     Bounces Traffic Server on the local node. Bouncing Traffic Server shuts down 
+    and immediately restarts the Traffic Server node.
+    
+    
+
+ ` traffic_line -c` 
+
+:   
+    
+     Clears accumulated statistics on the local node.
+    
+    
+
+ ` traffic_line -h` 
+
+:   
+    
+     Displays a list of Traffic Line commands.
+    
+    
+
+ ` traffic_line -p _socket_path_` 
+
+:   
+    
+     Specifies location (directory and path) of the socket used for Traffic Line communication.  
+     The default path is: `_install_dir_ /config/cli` 
+    
+    
+
+ ` traffic_line -q` 
+
+:   
+    
+     Displays a list of the origin servers that are currently congested. 
+    
+    
+                  
+    
+     **Note:** To use this command, you must set the variable ` _proxy.config.raf.enabled_` 
+    to 1 and set the variable ` _proxy.config.raf.port_` to a different port _ 
+    only_ if there is a conflict with the default port 9000.
+    
+    
+
+ ` traffic_line -r _variable_` 
+
+:   
+    
+     Displays specific performance statistics or a current configuration setting. 
+    For a list of the variables you can specify, see [Traffic Line Variables](cli.htm#1025718). 
+    
+    
+    
+
+ ` traffic_line -s _variable_ -v _value_` 
+
+:   
+    
+     Sets configuration variables, where `_variable_` is the configuration variable 
+    you want to change and ` _value_` is the value you want to set. Refer to [records.config](files.htm#records.config) 
+    for a list of the configuration variables you can specify.
+    
+    
+
+ ` traffic_line -x` 
+
+:   
+    
+     Initiates a Traffic Server configuration file reread. Use this command after 
+    every configuration file modification.
+    
+    
+
+ ` traffic_line -B` 
+
+:   
+    
+     Bounces all Traffic Server nodes in the cluster. Bouncing Traffic Server shuts 
+    down and immediately restarts Traffic Server, node-by-node.
+    
+    
+
+ ` traffic_line -C` 
+
+:   
+    
+     Clears accumulated statistics on all nodes in the cluster.
+    
+    
+
+ ` traffic_line -L` 
+
+:   
+    
+     Restarts the ` traffic_manager` and ` traffic_server` processes on the local 
+    node.
+    
+    
+
+ ` traffic_line -M` 
+
+:   
+    
+     Restarts the ` traffic_manager` process and the ` traffic_server` process 
+    on all the nodes in a cluster.
+    
+    
+
+ ` traffic_line -S` 
+
+:   
+    
+     Shuts down Traffic Server on the local node.
+    
+    
+
+ ` traffic_line -U` 
+
+:   
+    
+     Starts Traffic Server on the local node.
+    
+    
+
+        **Traffic Line Variables**
+  
+
+  
+
+ You can view statistics and change configuration options in Traffic Line by 
+using specific variables. The variables used for gathering statistics are described 
+below. The variables used for viewing and changing configuration options are 
+described in [records.config](files.htm#records.config). For procedures about 
+specifying the variables, refer to [Viewing Statistics from Traffic Line](monitor.htm) 
+and [Configuring Traffic Server Using Traffic Line](configure.htm). 
+
+ The variables used for viewing individual statistics are described in the 
+following table. To view a statistic in Traffic Line, enter the command `traffic_line 
+-r _variable_ `at the prompt. 
+
+     
+
+** Statistic**
+
+:   
+    
+    ** Variable**
+    
+    
+
+** Summary**
+
+ Node name
+
+:   
+    
+     _` proxy.node.hostname ` _
+    
+    
+
+ Objects served
+
+:   
+    
+     _` proxy.node.user_agents_total_documents_served` _
+    
+    
+
+ Transactions per second
+
+:   
+    
+     _` proxy.node.user_agent_xacts_per_second` _
+    
+    
+
+** Node**
+
+ Document hit rate 
+
+:   
+    
+     _` proxy.node.cache_hit_ratio_avg_10s` _
+    
+    
+                 
+    
+     _` proxy.cluster.cache_hit_ratio_avg_10s` _
+    
+    
+
+ Bandwidth savings 
+
+:   
+    
+     _` proxy.node.bandwidth_hit_ratio_avg_10s` _
+    
+    
+                 
+    
+     _` proxy.cluster.bandwidth_hit_ratio_avg_10s ` _
+    
+    
+
+ Cache percent free
+
+:   
+    
+     _` proxy.node.cache.percent_free` _
+    
+    
+                 
+    
+     _` proxy.cluster.cache.percent_free` _
+    
+    
+
+ Open origin server connections
+
+:   
+    
+     _` proxy.node.current_server_connections` _
+    
+    
+                 
+    
+     _` proxy.cluster.current_server_connections ` _
+    
+    
+
+ Open client connections 
+
+:   
+    
+     _` proxy.node.current_client_connections` _
+    
+    
+                 
+    
+     _` proxy.cluster.current_client_connections ` _
+    
+    
+
+ Cache transfers in progress 
+
+:   
+    
+     _` proxy.node.current_cache_connections` _
+    
+    
+                 
+    
+     _` proxy.cluster.current_cache_connections ` _
+    
+    
+
+ Client throughput (Mbits/sec)
+
+:   
+    
+     _` proxy.node.client_throughput_out` _
+    
+    
+                 
+    
+     _` proxy.cluster.client_throughput_out` _
+    
+    
+
+ Transactions per second 
+
+:   
+    
+     _` proxy.node.user_agent_xacts_per_second ` _
+    
+    
+                 
+    
+     _` proxy.cluster.user_agent_xacts_per_second` _
+    
+    
+
+ DNS lookups per second 
+
+:   
+    
+     _` proxy.node.dns.lookups_per_second ` _
+    
+    
+                 
+    
+     _` proxy.cluster.dns.lookups_per_second ` _
+    
+    
+
+ Host database hit rate 
+
+:   
+    
+     _` proxy.node.hostdb.hit_ratio_avg_10s` _
+    
+    
+                 
+    
+     _` proxy.cluster.hostdb.hit_ratio_avg_10s ` _
+    
+    
+
+** HTTP**
+
+ Total document bytes from client
+
+:   
+    
+     _` proxy.process.http.user_agent_response_document_total_size` _
+    
+    
+
+ Total header bytes from client
+
+:   
+    
+     _` proxy.process.http.user_agent_response_header_total_size` _
+    
+    
+
+ Total connections to client
+
+:   
+    
+     _` proxy.process.http.total_client_connections` _
+    
+    
+
+ Client transactions in progress
+
+:   
+    
+     _` proxy.process.http.current_client_transactions` _
+    
+    
+
+ Total document bytes from origin server
+
+:   
+    
+     _` proxy.process.http.origin_server_response_document_total_size` _
+    
+    
+
+ Total header bytes from origin server
+
+:   
+    
+     _` proxy.process.http.origin_server_response_header_total_size` _
+    
+    
+
+ Total connections to origin server
+
+:   
+    
+     _` proxy.process.http.total_server_connections` _
+    
+    
+
+ Origin server transactions in progress 
+
+:   
+    
+     _` proxy.process.http.current_server_transactions` _
+    
+    
+
+** ICP**
+
+ ICP query requests originating from this node
+
+:   
+    
+     _` proxy.process.icp.icp_query_requests` _
+    
+    
+
+ ICP query messages sent from this node
+
+:   
+    
+     _` proxy.process.icp.total_udp_send_queries` _
+    
+    
+
+ ICP peer hit messages received from this node
+
+:   
+    
+     _` proxy.process.icp.icp_query_hits` _
+    
+    
+
+ ICP peer miss messages received from this node 
+
+:   
+    
+     _` proxy.process.icp.icp_query_misses` _
+    
+    
+
+ Total ICP responses received from this node
+
+:   
+    
+     _` proxy.process.icp.icp_remote_responses` _
+    
+    
+
+ Average ICP message response time (ms) from this node
+
+:   
+    
+     _` proxy.process.icp.total_icp_response_time` _
+    
+    
+
+ Average ICP request time (ms) from this node
+
+:   
+    
+     _` proxy.process.icp.total_icp_request_time` _
+    
+    
+
+ Query messages received from ICP peers
+
+:   
+    
+     _` proxy.process.icp.icp_remote_query_requests` _
+    
+    
+
+ Remote query hits from ICP peers
+
+:   
+    
+     _` proxy.process.icp.cache_lookup_success` _
+    
+    
+
+ Remote query misses from ICP peers
+
+:   
+    
+     _` proxy.process.icp.cache_lookup_fail` _
+    
+    
+
+ Successful response messages sent to peers
+
+:   
+    
+     _` proxy.process.icp.query_response_write` _
+    
+    
+
+** Cache **
+
+ Bytes used
+
+:   
+    
+     _` proxy.process.cache.bytes_used` _
+    
+    
+
+ Cache size
+
+:   
+    
+     _` proxy.process.cache.bytes_total` _
+    
+    
+
+ Lookups in progress
+
+:   
+    
+     _` proxy.process.cache.lookup.active` _
+    
+    
+
+ Lookups completed
+
+:   
+    
+     _` proxy.process.cache.lookup.success` _
+    
+    
+
+ Lookup misses
+
+:   
+    
+     _` proxy.process.cache.lookup.failure` _
+    
+    
+
+ Reads in progress
+
+:   
+    
+     _` proxy.process.cache.read.active` _
+    
+    
+
+ Reads completed
+
+:   
+    
+     _` proxy.process.cache.read.success` _
+    
+    
+
+ Read misses
+
+:   
+    
+     _` proxy.process.cache.read.failure` _
+    
+    
+
+ Writes in progress
+
+:   
+    
+     _` proxy.process.cache.write.active` _
+    
+    
+
+ Writes completed
+
+:   
+    
+     _` proxy.process.cache.write.success` _
+    
+    
+
+ Write failures
+
+:   
+    
+     _` proxy.process.cache.write.failure` _
+    
+    
+
+ Updates in progress
+
+:   
+    
+     _` proxy.process.cache.update.active` _
+    
+    
+
+ Updates completed
+
+:   
+    
+     _` proxy.process.cache.update.success` _
+    
+    
+
+ Update failures
+
+:   
+    
+     _` proxy.process.cache.update.failure` _
+    
+    
+
+ Removes in progress
+
+:   
+    
+     _` proxy.process.cache.remove.active` _
+    
+    
+
+ Remove successes
+
+:   
+    
+     _` proxy.process.cache.remove.success` _
+    
+    
+
+ Remove failures
+
+:   
+    
+     _` proxy.process.cache.remove.failure` _
+    
+    
+
+ ** Host Database** 
+
+ Total lookups
+
+:   
+    
+     _` proxy.process.hostdb.total_lookups` _
+    
+    
+
+ Total hits
+
+:   
+    
+     _` proxy.process.hostdb.total_hits` _
+    
+    
+
+ Time TTL (min)
+
+:   
+    
+     _` proxy.process.hostdb.ttl` _
+    
+    
+
+ ** DNS** 
+
+ DNS total lookups
+
+:   
+    
+     _` proxy.process.dns.total_dns_lookups` _
+    
+    
+
+ Average lookup time (msec)
+
+:   
+    
+     _` proxy.process.dns.lookup_avg_time` _
+    
+    
+
+ DNS successes
+
+:   
+    
+     _` proxy.process.dns.lookup_successes` _
+    
+    
+
+** Cluster **
+
+ Bytes read
+
+:   
+    
+     _` proxy.process.cluster.read_bytes` _
+    
+    
+
+ Bytes written
+
+:   
+    
+     _` proxy.process.cluster.write_bytes` _
+    
+    
+
+ Connections open
+
+:   
+    
+     _` proxy.process.cluster.connections_open` _
+    
+    
+
+ Total operations
+
+:   
+    
+     _` proxy.process.cluster.connections_opened` _
+    
+    
+
+ Network backups
+
+:   
+    
+     _` proxy.process.cluster.net_backup` _
+    
+    
+
+ Clustering nodes
+
+:   
+    
+     _` proxy.process.cluster.nodes` _
+    
+    
+
+** Logging **
+
+ Log files currently open
+
+:   
+    
+     _` proxy.process.log.log_files_open` _
+    
+    
+
+ Space used for log files
+
+:   
+    
+     _` proxy.process.log.log_files_space_used` _
+    
+    
+
+ Number of access events logged
+
+:   
+    
+     _` proxy.process.log.event_log_access` _
+    
+    
+
+ Number of access events skipped
+
+:   
+    
+     _` proxy.process.log.event_log_access_skip` _
+    
+    
+
+ Number of error events logged
+
+:   
+    
+     _` proxy.process.log.event_log_error` _
+    
+    
+
+** Congestion Control**
+
+ Number of congestions Traffic Server has observed because the maximum number 
+of connections was exceeded.
+
+:   
+    
+     _`proxy.process.congestion.congested_on_max_connection`_
+    
+    
+
+ Number of congestions Traffic Server has observed because of an OS response 
+or timeout failure.
+
+:   
+    
+    _`proxy.process.congestion.congested_on_conn_failures`_
+    
+    
+
+      
+
+   
+
+   
+
+         
+
+* [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/traffic-server-error-messages/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext?rev=1070302&view=auto
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext (added)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext Sun Feb 13 21:38:37 2011
@@ -0,0 +1,1021 @@
+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 F - Traffic Server Error Messages   # {#AppendixF-TSErrorMessages}
+
+ This appendix contains the following sections:
+
+* [Traffic Server Error Messages](#57301): describes the warning messages Traffic Server sends to the system log file.
+* [Traffic Server Alarm Messages](#65686): describes the alarm messages that may appear on Traffic Manager Monitor pages.
+* [HTML Messages Sent to Clients](#55499): describes the HTML error messages Traffic Server sends to browser clients.
+* [Standard HTTP Response Messages](#55388): describes the standard HTTP response codes origin servers send to browser clients.
+
+##         Traffic Server Error Messages      ## {#TSErrorMessages}
+
+The following table lists messages that can appear in system log files. This 
+list is not exhaustive; it simply describes common warning messages that can 
+occur and which might require your attention. 
+
+     
+
+###         Traffic Server Process Fatal      ### {#TSProcessFatal}
+
+     ** 
+
+ Message
+
+** ** 
+
+ Description
+
+** 
+
+ `Accept port is not between 1 and 65535. Please check configuration`
+
+:   
+    
+     The port specified in the ` records.config` file that accepts incoming HTTP 
+    requests is not valid. 
+    
+    
+
+ `Self loop is detected in parent proxy configuration`
+
+:   
+    
+     The name and port of the parent proxy match that of Traffic Server. This creates 
+    a loop when Traffic Server attempts to send the request to the parent proxy. 
+     
+    
+    
+
+###         Traffic Server Warnings      ### {#TSWarnings}
+
+     ** 
+
+ Message
+
+** ** 
+
+ Description
+
+** 
+
+ `_ Logfile_ error: _ error_number_ `
+
+:   
+    
+     Generic logging error.
+    
+    
+
+` Bad cluster major version range _ version1_ -_ version2_ for node _ IP address_ 
+connect failed`
+
+:   
+    
+     Incompatible software versions causing a problem.
+    
+    
+
+` Can't open config file _ filename_ for reading custom formats`
+
+:   
+    
+     Custom logging is enabled, but Traffic Server cannot find the ` logs.config` 
+    file. 
+    
+    
+
+` Connect by disallowed client _ IP address_, closing`
+
+:   
+    
+     The specified client is not allowed to connect to Traffic Server; the client 
+    IP address is not listed in the ` ip_allow.config` file. 
+    
+    
+
+ Could not rename log_ `filename`_ to _ `rolled filename`_ 
+
+:   
+    
+     System error when renaming log file during roll. 
+    
+    
+
+` Did _ this_amount_ of backup; still to do _ remaining_amount_ `
+
+:   
+    
+     Congestion is approaching.
+    
+    
+
+` Different clustering minor versions _ version1_ , _ version2_ for node _ 
+IP address_ continuing`
+
+:   
+    
+     Incompatible software versions are causing a problem. 
+    
+    
+
+` Log format symbol _ symbol_name_ not found`
+
+:   
+    
+     Custom log format references a field symbol that does not exist. Refer to 
+    [Event Logging Formats](logfmts.htm).
+    
+    
+
+` Missing field for field marker`
+
+:   
+    
+     Error reading a log buffer.
+    
+    
+
+` Unable to open log file_ filename_, errno=_ error_number_ `
+
+:   
+    
+     Cannot open the log file.
+    
+    
+
+` Error accessing disk _ disk_name_ `
+
+:   
+    
+     Traffic Server might have a cache read problem. You might need to replace 
+    the disk.
+    
+    
+
+` Too many errors accessing disk _ disk_name_ : declaring disk bad`
+
+:   
+    
+     Traffic Server is not using the cache disk because it encountered too many 
+    errors. The disk might be corrupt and might have to be replaced.
+    
+    
+
+` No cache disks specified in storage.config file: cache disabled`
+
+:   
+    
+     The Traffic Server ` storage.config` file does not list any cache disks; Traffic 
+    Server is running in proxy-only mode. You must add the disks you want to use 
+    for the cache to the [storage.config](files.htm#storage.config) file.
+    
+    
+
+## Traffic Server Alarm Messages ## {#TSAlarmMessages}
+
+     
+
+  
+
+     ** 
+
+ Message
+
+** ** 
+
+ Description
+
+** 
+
+` [Rollback::Rollback] Config file is read-only:_ filename_`
+
+:   
+    
+     Go to the Traffic Server ` config` directory and check the indicated file 
+    permissions; change if necessary. 
+    
+    
+
+` [Rollback::Rollback] Unable to read or write config file_ filename_`
+
+:   
+    
+     Go to the Traffic Server ` config` directory and make sure the indicated file 
+    exists. Check permissions and modify if necessary. 
+    
+    
+
+` [Traffic Manager] Configuration File Update Failed: _ error_number_ `
+
+:   
+    
+     Go to the Traffic Server ` config` directory and check the indicated file 
+    permissions; change if necessary. 
+    
+    
+
+` [Traffic Manager] Mgmt <==>Proxy conn. closed`
+
+:   
+    
+     An informational message to inform you that the ` traffic_server` process 
+    is down. 
+    
+    
+
+` Access logging suspended - configured space allocation exhausted. `
+
+:   
+    
+     The space allocated to the event log files is full; you must either increase 
+    the space or delete some log files so that access logging to continue. To prevent 
+    this error, consider rolling log files more frequently and enabling the autodelete 
+    feature. 
+    
+    
+
+` Access logging suspended - no more space on the logging partition.`
+
+:   
+    
+     The entire partition containing the event logs is full; you must delete or 
+    move some log files to enable access logging to continue. To prevent this error, 
+    consider rolling log files more frequently and enabling the autodelete feature. 
+     
+    
+    
+
+` Created zero length place holder for config file_ filename_ `
+
+:   
+    
+     Go to the Traffic Server ` config` directory and check the indicated file. 
+    If it is indeed zero in length, then use a backup copy of the configuration 
+    file. 
+    
+    
+
+` Traffic Server can't open_ filename _for reading custom formats`
+
+:   
+    
+     Make sure the ` _proxy.config.log.config_file_` variable in the ` records.config` 
+    file contains the correct path to the custom log configuration file (the default 
+    is` logging/logs.config` ). 
+    
+    
+
+` Traffic Server could not open logfile _ filename_ `
+
+:   
+    
+     Check permissions for the indicated file and the logging directory. 
+    
+    
+
+` Traffic Server failed to parse line _ line_number_ of the logging config 
+file_ filename_`
+
+:   
+    
+     Check your custom log configuration file; there could be syntax errors. Refer 
+    to [ Custom Logging Fields](logfmts.htm#66912) for correct custom log format 
+    fields. 
+    
+    
+
+ `vip_config binary is not setuid root, manager will be unable to enable virtual 
+ip addresses`
+
+:   
+    
+     The ` traffic_manager` process is not able to set virtual IP addresses. You 
+    must `setuid root `for the ` vip_config` file in the Traffic Server ` bin` 
+    directory. 
+    
+    
+
+##         HTML Messages Sent to Clients      ## {#HTMLMessagesSentClients}
+
+Traffic Server returns detailed error messages to browser clients when there 
+are problems with the HTTP transactions requested by the browser. These Traffic 
+Server response messages correspond to standard HTTP response codes, but provide 
+more information. A list of the more frequently-encountered HTTP response codes 
+is provided in [Standard HTTP Response Messages](#55388). You can customize 
+the Traffic Server response messages, if desired.
+
+The following table lists the hard-coded Traffic Server HTTP messages, with 
+corresponding HTTP response codes and customizable files. 
+
+      ** 
+
+ Title 
+
+** ** 
+
+ HTTP Code
+
+** ** 
+
+ Description
+
+** ** 
+
+ Customizable Filename
+
+** 
+
+` Access Denied`
+
+:   
+    
+    ` 403`
+    
+    :   
+    
+     You are not allowed to access the document at location `_ URL_` . 
+    
+    :   
+    
+    ` access#denied`
+    
+    
+
+` Cache Read Error`
+
+:   
+    
+    ` 500`
+    
+    :   
+    
+     Error reading from cache; please retry request.
+    
+    :   
+    
+    ` cache#read_error`
+    
+    
+
+` Connection Timed Out`
+
+:   
+    
+    ` 504`
+    
+    :   
+    
+     Too much time has elapsed since the server has sent data. 
+    
+    :   
+    
+    ` timeout#inactivity`
+    
+    
+
+` Content Length Required`
+
+:   
+    
+    ` 400`
+    
+    :   
+    
+     Could not process this request because `Content-Length` was not specified. 
+    
+    
+    :   
+    
+    ` request#no_content_length`
+    
+    
+
+` Cycle Detected`
+
+:   
+    
+    ` 400`
+    
+    :   
+    
+     Your request is prohibited because it would cause an HTTP proxy cycle. 
+    
+    :   
+    
+    ` request#cycle_detected`
+    
+    
+
+` Forbidden`
+
+:   
+    
+    ` 403`
+    
+    :   
+    
+     `_ port_number_` is not an allowed port for SSL connections (you have made 
+    a request for a secure SSL connection to a forbidden port number).
+    
+    :   
+    
+    ` access#ssl_forbidden`
+    
+    
+
+` Host Header Required`
+
+:   
+    
+    ` 400`
+    
+    :   
+    
+     An attempt was made to transparently proxy your request, but this attempt 
+    failed because your browser did not send an HTTP ` Host` header. Manually configure 
+    your browser to use ` http://` `_ proxy_name_` :`_ proxy_port_` as the HTTP 
+    proxy. Alternatively, end users can upgrade to a browser that supports the 
+    HTTP ` Host` header field.
+    
+    :   
+    
+    ` interception#no_host`
+    
+    
+
+` Host Header Required`
+
+:   
+    
+    ` 400`
+    
+    :   
+    
+     Because your browser did not send a `Host` HTTP header field, the virtual 
+    host being requested could not be determined. To access the website correctly, 
+    you must upgrade to a browser that supports the HTTP `Host` header field.
+    
+    :   
+    
+    ` request#no_host`
+    
+    
+
+` HTTP Version Not Supported`
+
+:   
+    
+    ` 505`
+    
+    :   
+    
+     The origin server _` server_name`_ is using an unsupported version of the 
+    HTTP protocol.
+    
+    :   
+    
+    ` response#bad_version`
+    
+    
+
+` Invalid HTTP Request`
+
+:   
+    
+    ` 400`
+    
+    :   
+    
+     Could not process this `_ client_request_` HTTP method request for _` URL`_ 
+    .
+    
+    :   
+    
+    ` request#syntax_error`
+    
+    
+
+` Invalid HTTP Response`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     The host `_ server_name_` did not return the document `_ URL_` correctly. 
+    
+    
+    :   
+    
+    ` response#bad_response`
+    
+    
+
+` Malformed Server Response`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     The host `_ server_name_` did not return the document `_ URL_` correctly. 
+    
+    
+    :   
+    
+    ` response#bad_response`
+    
+    
+
+` Malformed Server Response Status`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     The host `_ server_name _` did not return the document `_ URL _` correctly. 
+    
+    
+    :   
+    
+    ` response#bad_response`
+    
+    
+
+` Maximum Transaction Time exceeded`
+
+:   
+    
+    ` 504`
+    
+    :   
+    
+     Too much time has elapased while transmitting document `_ URL_` .
+    
+    :   
+    
+    ` timeout#activity`
+    
+    
+
+` No Response Header From Server`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     The host `_ server_name _` did not return the document `_ URL_` correctly. 
+    
+    
+    :   
+    
+    ` response#bad_response`
+    
+    
+
+` Not Cached`
+
+:   
+    
+    ` 504`
+    
+    :   
+    
+     This document was not available in the cache, and you (the client) only accept 
+    cached copies.
+    
+    :   
+    
+    ` cache#not_in_cache`
+    
+    
+
+` Not Found on Accelerator`
+
+:   
+    
+    ` 404`
+    
+    :   
+    
+     The request for `_ URL_` on host `_ server_name _` was not found. Check the 
+    location and try again.
+    
+    :   
+    
+    ` urlrouting#no_mapping`
+    
+    
+
+` NULL`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     The host `_ hostname_` did not return the document `_ URL_` correctly.
+    
+    :   
+    
+    ` response#bad_response`
+    
+    
+
+` Proxy Authentication Required`
+
+:   
+    
+    ` 407`
+    
+    :   
+    
+     Please log in with username and password.
+    
+    :   
+    
+    ` access#proxy_auth_required`
+    
+    
+
+` Server Hangup`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     The server `_ hostname_` closed the connection before the transaction was 
+    completed.
+    
+    :   
+    
+    ` connect#hangup`
+    
+    
+
+` Temporarily Moved`
+
+:   
+    
+    ` 302`
+    
+    :   
+    
+     The document you requested,`_ URL_` , has moved to a new location. The new 
+    location is `_ new_URL_` .
+    
+    :   
+    
+    ` redirect#moved_temporarily`
+    
+    
+
+` Transcoding Not Available`
+
+:   
+    
+    ` 406`
+    
+    :   
+    
+     Unable to provide the document `_ URL_` in the format requested by your browser. 
+    
+    
+    :   
+    
+    ` transcoding#unsupported`
+    
+    
+
+` Tunnel Connection Failed`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     Could not connect to the server `_ hostname_` .
+    
+    :   
+    
+    ` connect#failed_connect`
+    
+    
+
+` Unknown Error`
+
+:   
+    
+    ` 502`
+    
+    :   
+    
+     The host `_ hostname_` did not return the document `_ URL_` correctly.
+    
+    :   
+    
+    ` response#bad_response`
+    
+    
+
+` Unknown Host`
+
+:   
+    
+    ` 500`
+    
+    :   
+    
+     Unable to locate the server named `_ hostname_`; the server does not have 
+    a DNS entry. Perhaps there is a misspelling in the server name or the server 
+    no longer exists; double-check the name and try again. 
+    
+    :   
+    
+    ` connect#dns_failed`
+    
+    
+
+` Unsupported URL Scheme`
+
+:   
+    
+    ` 400`
+    
+    :   
+    
+     Cannot perform your request for the document `_ URL_` because the protocol 
+    scheme is unknown.
+    
+    :   
+    
+    ` request#scheme_unsupported`
+    
+    
+
+###         Standard HTTP Response Messages        ### {#StandardHTTPResponseMessages}
+
+The following standard HTTP response messages are provided for your information. 
+ 
+
+    
+    ** 
+
+ Message
+
+** ** 
+
+ Description
+
+** 
+
+**` 200`**
+
+:   
+    
+     OK
+    
+    
+
+**` 202`**
+
+:   
+    
+     Accepted
+    
+    
+
+**` 204`**
+
+:   
+    
+     No Content
+    
+    
+
+**` 206`**
+
+:   
+    
+     Partial Content
+    
+    
+
+**` 300 `**
+
+:   
+    
+     Multiple Choices
+    
+    
+
+**` 301`**
+
+:   
+    
+     Moved Permanently
+    
+    
+
+**` 302`**
+
+:   
+    
+     Found
+    
+    
+
+**` 303`**
+
+:   
+    
+     See Other
+    
+    
+
+**` 304`**
+
+:   
+    
+     Not Modified
+    
+    
+
+**` 400`**
+
+:   
+    
+     Bad Request
+    
+    
+
+**` 401`**
+
+:   
+    
+     Unauthorized; retry
+    
+    
+
+**` 403`**
+
+:   
+    
+     Forbidden
+    
+    
+
+**` 404`**
+
+:   
+    
+     Not Found
+    
+    
+
+**` 405`**
+
+:   
+    
+     Method Not Allowed
+    
+    
+
+**` 406`**
+
+:   
+    
+     Not acceptable
+    
+    
+
+**` 408`**
+
+:   
+    
+     Request Timeout
+    
+    
+
+**` 500`**
+
+:   
+    
+     Internal server error
+    
+    
+
+**` 501 `**
+
+:   
+    
+     Not Implemented
+    
+    
+
+**` 502`**
+
+:   
+    
+     Bad Gateway
+    
+    
+
+**` 504`**
+
+:   
+    
+     Gateway Timeout
+    
+    
+
+      
+
+   
+
+   
+
+         
+
+* [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