You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ig...@apache.org on 2011/03/10 02:00:54 UTC
svn commit: r1080086 - in
/trafficserver/site/branches/ats-cms/content/docs/trunk/admin:
cluster-howto/index.en.mdtext http-proxy-caching/index.en.mdtext
monitoring-traffic/index.en.mdtext
traffic-server-error-messages/index.en.mdtext
Author: igalic
Date: Thu Mar 10 01:00:54 2011
New Revision: 1080086
URL: http://svn.apache.org/viewvc?rev=1080086&view=rev
Log:
Removing logo, doing some markdown fixing:
Error Messages are mostly done.
Modified:
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext
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/index.en.mdtext
trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext?rev=1080086&r1=1080085&r2=1080086&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/cluster-howto/index.en.mdtext Thu Mar 10 01:00:54 2011
@@ -23,7 +23,7 @@ Traffic Server scales from a single node
cluster allowing you to improve system performance and reliability. This
chapter discusses the following topics:
-[TOC]
+[TOC](#toc)
### Understanding Traffic Server Clusters ### {#UnderstandingTSClusters}
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/http-proxy-caching/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/http-proxy-caching/index.en.mdtext?rev=1080086&r1=1080085&r2=1080086&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/http-proxy-caching/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/http-proxy-caching/index.en.mdtext Thu Mar 10 01:00:54 2011
@@ -56,13 +56,7 @@ object in its object database (**cache**
if the object is fresh enough to serve. If it is fresh, then Traffic Server
serves it to the user as a **cache hit** (see the figure below).
-
-
->
->
->
-> _**A cache hit**_
->
+
**Step 4** If the data in the cache is stale, then Traffic Server connects
to the origin server and checks if the object is still fresh (a **revalidation**).
@@ -76,13 +70,8 @@ the user and the Traffic Server local ca
requests for the object can be served faster because the object is retrieved
directly from cache.
-
+
->
->
->
-> _**A cache miss**_
->
Caching is typically more complex than the preceding overview suggests. In
particular, the overview does not discuss how Traffic Server ensures freshness,
@@ -178,6 +167,7 @@ Server to cache only HTTP objects with `
the cache hit rate will be noticeably reduced (since very few objects will
have explicit expiration information).
+
##### To configure Traffic Server to cache objects with specific headers: ##### {#configureTScacheobjectswithspecificheaders}
1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory.
@@ -775,8 +765,6 @@ of an object allowed in the cache.
### Limiting the Number of Alternates for an Object ### {#LimitingNumberofAlternatesforanObject}
-
-
You can limit the number of alternates Traffic Server can cache per object
(the default is 3).
@@ -789,34 +777,21 @@ available alternates in the object store
1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory.
2. Edit the following variable:
-3. **Variable** **Description**
-`_proxy.config.cache.limits.http.max_alts_`
-:
-
- Set this variable to specify the maximum number of alternate versions of an
+3. _`proxy.config.cache.limits.http.max_alts`_
+: Set this variable to specify the maximum number of alternate versions of an
object you want Traffic Server to cache. The default value is three.
-
-
-
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.
## Using Congestion Control ## {#UsingCongestionControl}
-
-
The **Congestion Control** option enables you to configure Traffic Server to
stop forwarding HTTP requests to origin servers when they become congested.
Traffic Server then sends the client a message to retry the congested origin
server later.
-
-
To use the **Congestion Control** option, you must perform the following tasks:
-
-
-
* Enable the Congestion Control option.
* Create rules in the `congestion.config` file to specify:
@@ -824,20 +799,14 @@ To use the **Congestion Control** option
the timeouts Traffic Server uses, depending on whether a server is congested
the page Traffic Server sends to the client when a server becomes congested
if Traffic Server tracks the origin servers per IP address or per hostname
-
+
##### To enable and configure the Congestion Control option : ##### {#enableconfigureCongestionControloption}
1. In a text editor, open the `records.config` file located in the Traffic Server `config` directory.
2. Edit the following variable:
-3. **Variable** **Description**
-`_proxy.config.http.congestion_control.enabled_`
-:
-
- Set this variable to 1 to enable the congestion control option.
-
-
-
+3. _`proxy.config.http.congestion_control.enabled`_
+ : Set this variable to 1 to enable the congestion control option.
4. Save and close the `records.config` file.
5. In a text editor, open the `congestion.config` file located in the Traffic Server `config` directory.
6. Enter rules to specify which origin servers are tracked for congestion and the timeout values Traffic Server uses to determine congestion. Refer to [congestion.config](files.htm#congestion.config) for the rule format.
@@ -845,40 +814,3 @@ To use the **Congestion Control** option
8. Navigate to the Traffic Server `bin` directory.
9. Run the command `traffic_line -x` to apply the configuration changes.
-
-
-
-
-
-
-
-
-* [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.
-
-
-
Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext?rev=1080086&r1=1080085&r2=1080086&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/monitoring-traffic/index.en.mdtext Thu Mar 10 01:00:54 2011
@@ -1,4 +1,4 @@
-Title: Monitoring Traffic
+Title: Apache Traffic Server - Monitoring Traffic
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
@@ -84,41 +84,3 @@ to the statistic you want to see.
`traffic_line -r proxy.node.http.cache_hit_ratio`
If the Traffic Server `bin` directory is not in your path, then prepend the Traffic Line command with `./` (for example: `./traffic_line -r _variable_`).
-
-
-
-
-
-
-
-
-
-* [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.
-
-
-
Modified: 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=1080086&r1=1080085&r2=1080086&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/traffic-server-error-messages/index.en.mdtext Thu Mar 10 01:00:54 2011
@@ -1,4 +1,4 @@
-Title: Error Messages
+Title: Apache Traffic Server - Error Messages
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
@@ -17,981 +17,398 @@ Notice: Licensed to the Apache Softwa
under the License.
-# Appendix F - Traffic Server Error Messages # {#AppendixF-TSErrorMessages}
+# Traffic Server Error Messages # {#AppendixF-TSErrorMessages}
- This appendix contains the following sections:
+This section 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): describes the warning messages Traffic Server sends to the system log file.
+* [Traffic Server Alarm Messages](#TSAlarmMessages): describes the alarm messages that may appear on Traffic Manager Monitor pages.
+* [HTML Messages Sent to Clients](#HTMLMessagesSentClients): describes the HTML error messages Traffic Server sends to browser clients.
+* [Standard HTTP Response Messages](#StandardHTTPResponseMessages): describes the standard HTTP response codes origin servers send to browser clients.
-## Traffic Server Error Messages ## {#TSErrorMessages}
+## 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.
+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}
- **
+### Traffic Server Process Fatal ### {#TSProcessFatal}
- Message
+**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.
- Description
-**
+`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.
- `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`
+### Traffic Server Warnings ### {#TSWarnings}
-:
-
- 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}
+_`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.
- Message
-** **
+`Can't open config file` _`filename`_ `for reading custom formats`
+: Custom logging is enabled, but Traffic Server cannot find the `logs.config`
+ file.
- Description
+`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.
- `_ Logfile_ error: _ error_number_ `
+`Did` _`this_amount`_ `of backup; still to do` _`remaining_amount`_
+: Congestion is approaching.
-:
-
- Generic logging error.
-
-
+`Different clustering minor versions` _`version1, version2`_ `for node` _`IP address`_ `continuing`
+: Incompatible software versions are causing a problem.
-` Bad cluster major version range _ version1_ -_ version2_ for node _ IP address_
-connect failed`
-:
-
- Incompatible software versions 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).
-` Can't open config file _ filename_ for reading custom formats`
+`Missing field for field marker`
+: Error reading a log buffer.
-:
-
- Custom logging is enabled, but Traffic Server cannot find the ` logs.config`
- file.
-
-
+`Unable to open log file` _`filename`_`, errno=`_`error_number`_
+: Cannot open the log file.
-` Connect by disallowed client _ IP address_, closing`
+`Error accessing disk` _`disk_name`_
+: Traffic Server might have a cache read problem. You might need to replace
+ the disk.
-:
-
- The specified client is not allowed to connect to Traffic Server; the client
- IP address is not listed in the ` ip_allow.config` file.
-
-
+`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.
- Could not rename log_ `filename`_ to _ `rolled filename`_
+`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.
-:
-
- System error when renaming log file during roll.
-
-
-` Did _ this_amount_ of backup; still to do _ remaining_amount_ `
+## Traffic Server Alarm Messages ## {#TSAlarmMessages}
-:
-
- Congestion is approaching.
-
-
-` Different clustering minor versions _ version1_ , _ version2_ for node _
-IP address_ continuing`
+`[Rollback::Rollback] Config file is read-only:` _`filename`_
+: Go to the Traffic Server `config` directory and check the indicated file
+ permissions; change if necessary.
-:
-
- Incompatible software versions are causing a problem.
-
-
+`[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.
-` Log format symbol _ symbol_name_ not found`
+`[Traffic Manager] Configuration File Update Failed:` _`error_number`_
+: Go to the Traffic Server `config` directory and check the indicated file
+ permissions; change if necessary.
-:
-
- Custom log format references a field symbol that does not exist. Refer to
- [Event Logging Formats](logfmts.htm).
-
-
+`[Traffic Manager] Mgmt <==>Proxy conn. closed`
+: An informational message to inform you that the `traffic_server` process
+ is down.
-` 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.
-
-
+`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.
-` 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.
-
-
+`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.
-` 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.
-
-
+`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 Alarm Messages ## {#TSAlarmMessages}
+`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.
-Â
- **
- Message
+## HTML Messages Sent to Clients ## {#HTMLMessagesSentClients}
-** **
-
- 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
+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](#StandardHTTPResponseMessages). 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.
+The following table lists the hard-coded Traffic Server HTTP messages, with
+corresponding HTTP response codes and customizable files.
- **
+`Access Denied`
+: `403`
+: You are not allowed to access the document at location _`URL`_ .
+: `access#denied`
- 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`
-
-
+`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`
-### Standard HTTP Response Messages ### {#StandardHTTPResponseMessages}
-The following standard HTTP response messages are provided for your information.
-
+`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`
-
- **
- Message
-** **
+`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`
- Description
-**
+`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`
-**` 200`**
-:
-
- OK
-
-
+`Invalid HTTP Request`
+: `400`
+: Could not process this _`client_request`_ HTTP method request for _`URL`_.
+: `request#syntax_error`
-**` 202`**
-:
-
- Accepted
-
-
-**` 204`**
+`Invalid HTTP Response`
+: `502`
+: The host _`server_name`_ did not return the document _`URL`_ correctly.
+: `response#bad_response`
-:
-
- No Content
-
-
-**` 206`**
+`Malformed Server Response`
+: `502`
+: The host _`server_name`_ did not return the document _`URL`_ correctly.
+: `response#bad_response`
-:
-
- Partial Content
-
-
-**` 300 `**
+`Malformed Server Response Status`
+: `502`
+: The host _`server_name`_ did not return the document _`URL`_ correctly.
+: `response#bad_response`
-:
-
- Multiple Choices
-
-
-**` 301`**
+`Maximum Transaction Time exceeded`
+: `504`
+: Too much time has elapased while transmitting document _`URL`_ .
+: `timeout#activity`
-:
-
- Moved Permanently
-
-
-**` 302`**
+`No Response Header From Server`
+: `502`
+: The host _`server_name`_ did not return the document _`URL`_ correctly.
+: `response#bad_response`
-:
-
- Found
-
-
-**` 303`**
+`Not Cached`
+: `504`
+: This document was not available in the cache, and you (the client) only accept
+ cached copies.
+: `cache#not_in_cache`
-:
-
- See Other
-
-
+`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`
-**` 304`**
+`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`
-:
-
- Not Modified
-
-
-**` 400`**
-:
-
- Bad Request
-
-
+### Standard HTTP Response Messages ### {#StandardHTTPResponseMessages}
-**` 401`**
+The following standard HTTP response messages are provided for your information.
-:
-
- Unauthorized; retry
-
-
+**`200`**
+: OK
-**` 403`**
+**`202`**
+: Accepted
-:
-
- Forbidden
-
-
+**`204`**
+: No Content
-**` 404`**
+**`206`**
+: Partial Content
-:
-
- Not Found
-
-
+**`300`**
+: Multiple Choices
-**` 405`**
+**`301`**
+: Moved Permanently
-:
-
- Method Not Allowed
-
-
-**` 406`**
+**`302`**
+: Found
-:
-
- Not acceptable
-
-
-**` 408`**
+**`303`**
+: See Other
-:
-
- Request Timeout
-
-
-**` 500`**
+**`304`**
+: Not Modified
-:
-
- Internal server error
-
-
+**`400`**
+: Bad Request
-**` 501 `**
+**`401`**
+: Unauthorized; retry
-:
-
- Not Implemented
-
-
+**`403`**
+: Forbidden
-**` 502`**
+**`404`**
+: Not Found
-:
-
- Bad Gateway
-
-
+**`405`**
+: Method Not Allowed
-**` 504`**
-:
-
- Gateway Timeout
-
-
+**`406`**
+: Not acceptable
-
-
-
+**`408`**
+: Request Timeout
-
+**`500`**
+: Internal server error
-* [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)
+**`501`**
+: Not Implemented
-
-
+**`502`**
+: Bad Gateway
- 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.
+**`504`**
+: Gateway Timeout