trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r1215072 - in /trafficserver/site/branches/ats-cms/content/docs/trunk: STATUS admin/configuration-files/records.config.en.mdtext admin/faqs/index.en.mdtext admin/working-log-files/squid-format.en.mdtext
Date Fri, 16 Dec 2011 09:36:43 GMT
Author: igalic
Date: Fri Dec 16 09:36:42 2011
New Revision: 1215072

URL: http://svn.apache.org/viewvc?rev=1215072&view=rev
Log:
Finished migrationg of FAQs. Some of them I have simply replaced
with a link to the docs, others I left as is.
Where the information, the question or the content was dubious,
obsolete or wrong, I just deleted the whole thing. Seriously, if your
server or browser does not support TLSv1, don't go online.

Modified:
    trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext
    trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/squid-format.en.mdtext

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS?rev=1215072&r1=1215071&r2=1215072&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/STATUS Fri Dec 16 09:36:42 2011
@@ -1,4 +1,4 @@
-Apache HTTP Traffic Server Trunk Documentation Status File.
+Apache Traffic Server Trunk Documentation Status File.
 Last modified: $Date: 2010-12-10 15:53:32 +0100 (Fri, 10 Dec 2010) $
 
 For more information on how to contribute to the Apache Traffic Server
@@ -9,8 +9,6 @@ Documentation Project, please see (LINK)
 To Do List
 =======================
 
-- integrate navigation/TOC generation
-
 - invent a wheel that will help translators and users spot out-dated documents
 
 - update the content: https://issues.apache.org/jira/secure/IssueNavigator.jspa?component=12313124
@@ -18,11 +16,6 @@ To Do List
 
 Migration procedure
 =======================
-- check out: https://github.com/igalic/HTML2Markdown
-
-- This requires Ruby 1.9.x
-
-- ex: ./html2markdown http://trafficserver.apache.org/docs/v2/sdk/HTTP_Transactions > http-hooks-and-transactions/http-transactions.en.mdtext
 
 - take a look at the chapters which are done already for inspiration.
 
@@ -33,8 +26,6 @@ Migration procedure
   This blog Post on the ASF CMS
   https://blogs.apache.org/infra/entry/the_asf_cms
 
-  https://issues.apache.org/jira/browse/TS-538 and it's ink-2-ts.sh
-
 
 Content Migration
 =======================
@@ -47,6 +38,8 @@ Findings
 
 - Make sure to put pictures in their own pragraph.
 
+- comments sometimes break markdown interpretation :-/
+
 
 Collision avoidance
 =====================
@@ -59,8 +52,8 @@ index - done
 getting-started - done
 http-proxy-caching - done
 reverse-proxy-http-redirects - done
-transparent-proxy - TS-488, needs review and info for other platforms
-forward-proxy - needs content.
+transparent-proxy - done - TS-488, needs review and info for other platforms
+forward-proxy - done
 explicit-proxy-caching - done
 hierachical-caching - done (commented out ICP peering, because it's not really supported right now)
 configuring-cache - done
@@ -73,7 +66,7 @@ traffic-line-commands - This needs work!
 event-logging-formats - done
 configuration-files - done
 traffic-server-error-messages - done
-faqs - restored. But it looks gross and needs serious cleanup.
+faqs - restored. cleaned up, needs a bit of a review.
 plugins - sort of done
 
 SDK Docs:

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext?rev=1215072&r1=1215071&r2=1215072&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/configuration-files/records.config.en.mdtext Fri Dec 16 09:36:42 2011
@@ -144,7 +144,7 @@ the `records.config` file.
 *`proxy.config.cop.core_signal`* {#proxy.config.cop.core_signal}
 :   `INT`
 :   Default: `0`
-:   The signal sent to `traffic_cop`'s managed processes to stop them. * 0 = no signal is sent.
+:   The signal sent to `traffic_cop`'s managed processes to stop them. `0` = no signal is sent.
 
 *`proxy.config.cop.linux_min_swapfree_kb`* {#proxy.config.cop.linux_min_swapfree_kb}
 :   `INT`
@@ -216,7 +216,7 @@ the `records.config` file.
 *`proxy.config.admin.user_id`* {#proxy.config.admin.user_id}
 :   `STRING`
 :   Default: `nobody`
-:   Option used to specify who to run the `traffic_server`process as; also used to specify ownership of config and log files.
+:   Option used to specify who to run the `traffic_server` process as; also used to specify ownership of config and log files.
 
     The nonprivileged user account designated to Traffic Server.
 
@@ -284,7 +284,7 @@ the `records.config` file.
     * `1` = all extra information is added.
     * `2` = some extra information is added.
 
-    Note: the Via: header string interpretation is [documented here.](../faqs#interpret_via_header)
+    Note: the Via: header string interpretation is [documented here.](../faqs#interpret-via)
 
 
 *`proxy.config.http.insert_response_via_str`* {#proxy.config.http.insert_response_via_str}

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext?rev=1215072&r1=1215071&r2=1215072&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/faqs/index.en.mdtext Fri Dec 16 09:36:42 2011
@@ -33,769 +33,548 @@ Link to documentation
 If a disk drive fails five successive I/O operations, then Traffic Server considers the drive inaccessible
 and removes the entire disk from the cache. Normal cache operations continue for all other Traffic Server disk drives.
 
-#### If a client disconnects during the time that Traffic Server is downloading a large object, is any of the object saved in the cache? #### {#client-disco-lo}
+## If a client disconnects during the time that Traffic Server is downloading a large object, is any of the object saved in the cache? ## {#client-disco-lo}
 
-When a client disconnects during an HTTP operation, Traffic Server continues 
-to download the object from the origin server for up to 10 seconds. If the 
-transfer from the origin server completes successfully within 10 seconds after 
-the client disconnect, then Traffic Server stores the object in cache. If the 
-origin server download does _not_ complete successfully within 10 seconds, 
-then Traffic Server disconnects from the origin server and deletes the object 
+When a client disconnects during an HTTP operation, Traffic Server continues
+to download the object from the origin server for up to 10 seconds. If the
+transfer from the origin server completes successfully within 10 seconds after
+the client disconnect, then Traffic Server stores the object in cache. If the
+origin server download does _not_ complete successfully within 10 seconds,
+then Traffic Server disconnects from the origin server and deletes the object
 from cache. Traffic Server does not store partial documents in the cache.
 
-#### Can Traffic Server cache Java applets, JavaScript programs, or other application files like VBScript? #### {#cache-java}
+## Can Traffic Server cache Java applets, JavaScript programs, or other application files like VBScript? ## {#cache-java}
 
 Yes, Traffic Server can store and serve Java applets, JavaScript programs, VBScripts, and other executable objects
 from its cache according to the freshness and cacheability rules for HTTP objects. Traffic Server does not execute
 the applets, scripts, or programs, however - these objects run only when the client system (ie, the one that sent the request) loads them.
 
 
-#### How do you apply changes to the `logs_xml.config` file to all nodes in a cluster? #### {#apply-logxml}
+## How do you apply changes to the `logs_xml.config` file to all nodes in a cluster? ## {#apply-logxml}
 
 Link to documentation
 
-#### In Squid- and Netscape-format log files, what do the cache result codes mean? #### {#squid-netscape-result-codes}
+## In Squid- and Netscape-format log files, what do the cache result codes mean? #### {#squid-netscape-result-codes}
 
-The following table describes the cache result codes in Squid and Netscape 
-log files.
+This is described in detail in the [Squid log format documentation](../working-log-files/squid-format)
 
-`TCP_HIT`
-:   A valid copy of the requested object was in the cache and Traffic Server sent 
-    the object to the client. 
-    
-`TCP_MISS`
-:   The requested object was not in cache, so Traffic Server retrieved the object 
-    from the origin server (or a parent proxy) and sent it to the client.
-
-`TCP_REFRESH_HIT `
-:   The object was in the cache, but it was stale. Traffic Server made an     
-    `if-modified-since` request to the origin server and the origin server sent a     
-    `304` not-modified response. Traffic Server sent the cached object to the client.
- 
-`TCP_REF_FAIL_HIT`
-:   The object was in the cache but was stale. Traffic Server made an     
-    `if-modified-since` request to the origin server but the server did not respond.
-    Traffic Server sent the cached object to the client.
-
-`TCP_REFRESH_MISS`
-:   The object was in the cache but was stale. Traffic Server made an     
-    `if-modified-since` request to the origin server and the server returned a new object.
-    Traffic Server served the new object to the client.
-
-`TCP_CLIENT_REFRESH`
-:   The client issued a request with a `no-cache` header. Traffic Server obtained 
-    the requested object from the origin server and sent a copy to the client. 
-    Traffic Server deleted the previous copy of the object from cache.
-
-`TCP_IMS_HIT`
-:   The client issued an     
-    `if-modified-since` request and the object was in cache & fresher than the IMS date, **or** an     
-    `if-modified-since` request to the origin server revealed the cached object was fresh.
-    Traffic Server served the cached object to the client.
-    
-`TCP_IMS_MISS`
-:   The client issued an     
-    `if-modified-since request`, and the object was either not in cache or was stale in cache. Traffic Server sent an     
-    `if-modified-since request` to the origin server and received the new object. Traffic Server sent the updated object to the client.
-    
-`TCP_SWAPFAIL`
-:   The object was in the cache but could not be accessed. The client did not 
-    receive the object.
-    
-`ERR_CLIENT_ABORT`
-:   The client disconnected before the complete object was sent.
-
-`ERR_CONNECT_FAIL`
-:   Traffic Server could not reach the origin server.
-
-`ERR_DNS_FAIL`
-:   The Domain Name Server (DNS) could not resolve the origin server name, or 
-    no DNS could be reached.
-
-`ERR_INVALID_REQ`
-:   The client HTTP request was invalid. (Traffic Server forwards requests with 
-    unknown methods to the origin server.) 
-
-`ERR_READ_TIMEOUT`
-:   The origin server did not respond to Traffic Server's request within the timeout 
-    interval.
-
-`ERR_PROXY_DENIED`
-:   Client service was denied.
+## What is recorded by the `cqtx` field in a custom log file? ## {#whatis-cqtx}
 
-
-`ERR_UNKNOWN`
-:   The client connected, but subsequently disconnected without sending a request. 
-
-#### What is recorded by the `cqtx` field in a custom log file? #### {#whatis-cqtx}
-
-* In **forward proxy mode**, the     
-      cqtx field records the complete client request in the log file (for example,     
+* In **forward proxy mode**, the
+      cqtx field records the complete client request in the log file (for example,
       GET http://www.company.com HTTP/1.0 ).
-* In **reverse proxy mode**, the     
+* In **reverse proxy mode**, the
       cqtx field records the hostname or IP address of the origin server because
-      Traffic Server first remaps the request as per map rules in the     
+      Traffic Server first remaps the request as per map rules in the
       [remap.config](../configuration-files/remap.config) file.
 
-#### Does Traffic Server refresh entries in its host database after a certain period of time if they have not been used? #### {#ts-refresh-hostdb}
+## Does Traffic Server refresh entries in its host database after a certain period of time if they have not been used? ## {#ts-refresh-hostdb}
 
-By default, the Traffic Server host database observes the time-to-live (`ttl`) 
-values set by name servers. You can reconfigure Traffic Server to ignore the 
-`ttl` set by name servers and use a specific Traffic Server setting instead. 
-Alternatively, you can configure Traffic Server to compare the `ttl` value 
-set by the name server with the `ttl` value set by Traffic Server, and then 
-use either the lower or the higher value. 
-
-#### To adjust the host database settings: #### {#adjusthostdatabasesettings}
-
-<!-- XXX: Put this into the records.config docs -->
-1. In a text editor, open the     
-                records.config file located in the Traffic Server     
-                config directory. 
-2.  Set the value of the variable     
-                proxy.config.hostdb.ttl_mode to:
-
-*         
-                  0 to obey `ttl` values set by the name servers.
-*         
-                  1 to ignore `ttl` values set by name servers and instead use the value set by the Traffic Server configuration variable     
-                proxy.config.hostdb.timeout (make sure you set this variable to a value appropriate for your needs).
-*         
-                2 to use the lower of the two values (i.e., either the value set by the name server or the one set by Traffic Server).
-*         
-                3 to use the higher of the two values.
-
- Save and close the     
-        records.config file.   
- From the Traffic Server     
-          bin directory, run the command     
-          traffic_line -x  to apply the configuration changes. 
+By default, the Traffic Server host database observes the time-to-live (`ttl`)
+values set by name servers. You can reconfigure Traffic Server to ignore the
+`ttl` set by name servers and use a specific Traffic Server setting instead.
+Alternatively, you can configure Traffic Server to compare the `ttl` value
+set by the name server with the `ttl` value set by Traffic Server, and then
+use either the lower or the higher value.
 
-#### Can you improve the look of your custom response pages by using images, animated .gifs, and Java applets? #### {#style-custom-pages}
+see [proxy.config.hostdb.ttl_mode](../configuration-files/records.config#proxy.config.hostdb.ttl_mode) for more info
+
+## Can you improve the look of your custom response pages by using images, animated .gifs, and Java applets? ## {#style-custom-pages}
 
-<!-- XXX: This sounds wrong. -->
 No, because Traffic Server can only respond to clients with a single text or HTML document.
 As a workaround, however, you can provide references on your custom response pages to images,
 animated .gifs, Java applets, or objects other than text which are located on a web server.
 Add links in the body_factory template files in the same way you would for any image in an HTML document (i.e., with the full URL in the `SRC` attribute).
 
-#### Can Traffic Server run in forward proxy and reverse proxy modes at the same time? #### {#run-forward-reverse-same-time}
-
-Yes. When you enable reverse proxy mode, Traffic Server remaps incoming requests according to the map rules in the     
-[`remap.config`](../configuration-files/remap.config) file. All other requests that do not match a map rule are simply served in forward proxy mode.
-
-If you want to run in reverse proxy only mode (wherein Traffic Server does _not_ serve requests that fail to match a map rule), then you must set the configuration variable     
-proxy.config.url_remap.remap_required to 1 in the [`records.config`](../configuration-files/records.config) file. 
+## Can Traffic Server run in forward proxy and reverse proxy modes at the same time? ## {#run-forward-reverse-same-time}
 
-#### How do I enable forward proxy mode #### {#forward-proxy}
+Yes. When you enable reverse proxy mode, Traffic Server remaps incoming requests
+according to the map rules in the [`remap.config`](../configuration-files/remap.config)
+file. All other requests that do not match a map rule are simply served in forward proxy mode.
 
-<!--- TODO: This should be it's own short document -->
+If you want to run in reverse proxy only mode (wherein Traffic Server does _not_ serve
+requests that fail to match a map rule), then you must set the configuration variable
+[proxy.config.url_remap.remap_required](../configuration-files/records.config#proxy.config.url_remap.remap_required)
+to `1` in the [`records.config`](../configuration-files/records.config) file.
 
-Forward proxy mode is not enabled out of the box for security reasons.
-When enabling any proxy on the internet, you want to make sure you observe
-pertinent security restrictions. Having an open proxy available to internet
-users is a bad thing. If you understand this and are sure you know what you are doing,
-in [`records.config`](../configuration-files/records.config):
 
-    ::::text
-    # Set this variable to 1 if you want Traffic Server to serve 
-    # requests only from origin servers listed in the mapping rules
-    # of the remap.config file. If a request does not match, then 
-    # the browser will receive an error.
-    CONFIG proxy.config.url_remap.remap_required INT 0
+## How do I enable forward proxy mode ## {#forward-proxy}
 
 
-#### How do I interpret the Via: header code? #### {#interpret-via}
+Please refer to the [Forward Proxy](../forward-proxy) documentation
 
-<!--- TODO: put this in records.config? -->
-The Via header is an optional HTTP header added by Traffic Server and other 
-HTTP proxies. If a request goes through multiple proxies, each one appends 
-its Via header content to the end of the existing Via header. Via header content 
-is for general information and diagnostic use only and should not be used as 
-a programmatic interface to Traffic Server. 
 
-The form of the Via header is 
+## How do I interpret the Via: header code? ## {#interpret-via}
 
-Via: _`<protocol> <proxyname>` (<product/version> [<via-codes>])_
+The Via header is an optional HTTP header added by Traffic Server and other
+HTTP proxies. If a request goes through multiple proxies, each one appends
+its Via header content to the end of the existing Via header. Via header content
+is for general information and diagnostic use only and should not be used as
+a programmatic interface to Traffic Server.
 
- _<protocol>_  the scheme and version of the HTTP request
+The form of the Via header is
 
- _<proxyname>_  the configured name of the proxy server
+    :::text
+    Via: <protocol> <proxyname> (<product/version> [<via-codes>]
 
- _<product/version>_  the Inktomi Network Products product name and version
+*  _<protocol>_  the scheme and version of the HTTP request
+*  _<proxyname>_  the configured name of the proxy server (defaults to the hostname of the machine where it was built)
+*  _<product/version>_  Traffic Server and its version
+*  _<via-codes>_  a string of alphabetic codes presenting status information about the proxy handling of the HTTP request
 
- _<via-codes>_  a string of alphabetic codes presenting status information about the proxy 
-handling of the HTTP request 
+For example:
 
- For example:
-
-    Via: HTTP/1.0 storm (Traffic-Server/4.0.0   [cMs f ]) 
+    :::text
+    Via: HTTP/1.0 storm (Traffic-Server/4.0.0   [cMs f ])
           [u lH o  f  pS eN]     cache hit
           [u lM oS fF pS eN]     cache miss
           [uN l oS f  pS eN]     no-cache origin server fetch
+
 The short status code shows the cache-lookup, server-info and cache-fill information as listed
-in the full status code description below. The long status code list provided in older,
-commercial versions of Traffic Server can be restored by setting the
-`verbose_via_str` config variable. 
+in the full status code description below. The long status code list can be achieved by
+setting [`proxy.config.http.insert_request_via_str`](../configuration-files/records.config#proxy.config.http.insert_request_via_str)
+to a higher value.
 
 The character strings in the via-code show `[<request results>:<proxy op>]` where _<request results>_
 represents status information about the results of the client request and _<proxy op>_ represent some
-information about the proxy operations performed during request processing. The full via-code status format is 
+information about the proxy operations performed during request processing. The full via-code status format is
+
+[[*u&lt;client-info&gt;*](#client-info) [*c&lt;cache-lookup&gt;*](#cache-lookup) [*s&lt;server-info&gt;*](#server-info) [*f&lt;cache-fill&gt;*](#cache-fill) [*p&lt;proxy-info&gt;*](#proxy-info) [*e&lt;error-codes&gt;*](#error-codes) [*:*](#separator) [*t&lt;tunnel-info&gt;*](#tunnel-info)[*c&lt;cache-type&gt;*](#cache-type)[*&lt;cache-lookup-result&gt;*](#cache-lookup-result) [*i&lt;icp-conn-info&gt;*](#icp-conn-info) [*p&lt;parent-proxy&gt;*](#parent-proxy) [*s&lt;server-conn-info&gt;*](#server-conn-info)]
+
+**u** _client-info_  Request headers received from client. Value is one of: {#client-info}
+
+C {#client-info-c}
+:    cookie
 
-_`[u<client-info> c<cache-lookup> s<server-info>`_
+E {#client-info-e}
+:    error in request
 
-f_<cache-fill>_ p_<proxy-info>_ e_<error-codes>_
+I {#client-info-i}
+:    If Modified Since (IMS)
 
-: t_<tunnel-info>_c_<cache-type><cache-lookup-result>_ i_<icp-conn-info>_ p_<parent-proxy>_ s_<server-conn-info>_]
+N {#client-info-n}
+:    no-cache
 
- **u** _client-info_  Request headers received from client. Value is one of:
+S {#client-info-s}
+:    simple request (not conditional)
 
- C 
-:    cookie 
+**c** _cache-lookup_  Result of Traffic Server cache lookup for URL. Value is one of: {#cache-lookup}
 
- E 
-:    error in request 
+A {#cache-lookup-a}
+:    in cache, not acceptable (a cache "MISS")
 
- I 
-:    If Modified Since (IMS) 
+H {#cache-lookup-h}
+:    in cache, fresh (a cache "HIT")
 
- N 
-:    no-cache 
+M {#cache-lookup-m}
+:    miss (a cache "MISS")
 
- S 
-:    simple request (not conditional) 
+S {#cache-lookup-s}
+:    in cache, stale (a cache "MISS")
 
- **c** _cache-lookup_  Result of Traffic Server cache lookup for URL. Value is one of:
+blank {#cache-lookup-blank}
+:    no cache lookup performed
 
- A 
-:    in cache, not acceptable (a cache "MISS") 
+**s** _server-info_  Response information received from origin server. Value is one of: {#server-info}
 
- H 
-:    in cache, fresh (a cache "HIT") 
+E {#server-info-e}
+:    error in response
 
- M 
-:    miss (a cache "MISS") 
+N {#server-info-n}
+:    not-modified
 
- S 
-:    in cache, stale (a cache "MISS") 
+S {#server-info-s}
+:    served
 
- blank 
-:    no cache lookup performed 
+blank {#server-info-blank}
+:    no server connection needed
 
- **s** _server-info_  Response information received from origin server. Value is one of:
+**f** _cache-fill_  Result of document write to cache. Value is one of: {#cache-fill}
 
- E 
-:    error in response 
+D {#cache-fill-d}
+:    cached copy deleted
 
- N 
-:    not-modified 
+U {#cache-fill-u}
+:    updated old cache copy
 
- S 
-:    served 
+W {#cache-fill-w}
+:    written into cache (new copy)
 
- blank 
-:    no server connection needed 
+blank {#cache-fill-blank}
+:    no cache write performed
 
- **f** _cache-fill_  Result of document write to cache. Value is one of:
 
- D 
-:    cached copy deleted 
+**p** _proxy-info_  Proxy operation result. Value is one of: {#proxy-info}
 
- U 
-:    updated old cache copy 
+N {#proxy-info-n}
+:    not-modified
 
- W 
-:    written into cache (new copy) 
+R {#proxy-info-r}
+:    origin server revalidated
 
- blank 
-:    no cache write performed 
+S {#proxy-info-s}
+:    served
 
- **p** _proxy-info_  Proxy operation result. Value is one of: 
- N 
-:    not-modified 
+**e** _error-codes_  Value is one of: {#error-codes}
 
- R 
-:    origin server revalidated 
+A {#error-codes-a}
+:    authorization failure
 
- S 
-:    served 
+C {#error-codes-c}
+:    connection to server failed
 
- **e** _error-codes_  Value is one of: 
- A 
-:    authorization failure 
+D {#error-codes-d}
+:    dns failure
 
- C 
-:    connection to server failed 
+F {#error-codes-f}
+:    request forbidden
 
- D 
-:    dns failure 
+H {#error-codes-h}
+:    header syntax unacceptable
 
- F 
-:    request forbidden 
+N {#error-codes-n}
+:    no error
 
- H 
-:    header syntax unacceptable 
+S {#error-codes-s}
+:    server related error
 
- N 
-:    no error 
+T {#error-codes-t}
+:    connection timed out
 
- S 
-:    server related error 
+**:** = Separates proxy request result information from operation detail codes {#separator}
 
- T 
-:    connection timed out 
+**t** _tunnel-info_  Proxy-only service operation. Value is one of: {#tunnel-info}
 
-**:** = Separates proxy request result information from operation detail codes 
+F {#tunnel-info-f}
+:    tunneling due to a header field (such as presence of If-Range header)
 
- **t** _tunnel-info_  Proxy-only service operation. Value is one of: 
- F 
-:    tunneling due to a header field (such as presence of If-Range header) 
+M {#tunnel-info-m}
+:    tunneling due to a method (e.g. CONNECT)
 
- M 
-:    tunneling due to a method (e.g. CONNECT) 
+O {#tunnel-info-o}
+:    tunneling because cache is turned off
 
- O 
-:    tunneling because cache is turned off 
+U {#tunnel-info-u}
+:    tunneling because of url (url suggests dynamic content)
 
- U 
-:    tunneling because of url (url suggests dynamic content) 
+blank {#tunnel-info-blank}
+:    no tunneling
 
- blank 
-:    no tunneling 
+**c** _cache-type_ and _cache-lookup_  cache result values (2 characters) {#cache-type}
 
- **c** _cache-type_ and _cache-lookup_  cache result values (2 characters) 
-  
-  cache-type character value is one of
+cache-type character value is one of
 
- C 
-:    cache 
+C {#cache-type-c}
+:    cache
 
- I 
-:    icp 
+I {#cache-type-i}
+:    icp
 
- blank 
-:    cache miss or no cache lookup 
+blank {#cache-type-blank}
+:    cache miss or no cache lookup
 
- cache-lookup-result character value is one of:  C 
-:    cache hit, but config forces revalidate 
+cache-lookup-result character value is one of: {#cache-lookup-result}
 
- D 
-:    cache hit, but method forces revalidated (e.g. ftp, not anonymous) 
+C {#cache-lookup-result-c}
+:    cache hit, but config forces revalidate
 
- H 
-:    cache hit 
+D {#cache-lookup-result-d}
+:    cache hit, but method forces revalidated (e.g. ftp, not anonymous)
 
- I 
-:    conditional miss (client sent conditional, fresh in cache, returned 412) 
+H {#cache-lookup-result-h}
+:    cache hit
 
- M 
-:    cache miss (url not in cache) 
+I {#cache-lookup-result-i}
+:    conditional miss (client sent conditional, fresh in cache, returned 412)
 
- N 
-:    conditional hit (client sent conditional, doc fresh in cache, returned 304) 
-     
+M {#cache-lookup-result-m}
+:    cache miss (url not in cache)
 
- S 
-:    cache hit, but expired 
+N {#cache-lookup-result-n}
+:    conditional hit (client sent conditional, doc fresh in cache, returned 304)
 
- U 
-:    cache hit, but client forces revalidate (e.g. Pragma: no-cache) 
+S {#cache-lookup-result-s}
+:    cache hit, but expired
 
- blank 
-:    no cache lookup 
+U {#cache-lookup-result-u}
+:    cache hit, but client forces revalidate (e.g. Pragma: no-cache)
 
- **i** _icp-conn-info_  ICP status
+blank {#cache-lookup-result-blank}
+:    no cache lookup
 
- F 
-:    connection open failed 
+**i** _icp-conn-info_  ICP status {#icp-conn-info}
 
- S 
-:    connection opened successfully 
+F {#icp-conn-info-f}
+:    connection open failed
 
- blank 
-:    no icp 
+S {#icp-conn-info-s}
+:    connection opened successfully
 
- **p** _parent-proxy_  parent proxy connection status 
- F 
-:    connection open failed 
+blank {#icp-conn-info-blank}
+:    no icp
 
- S 
-:    connection opened successfully 
+**p** _parent-proxy_  parent proxy connection status {#parent-proxy}
 
- blank 
-:    no parent proxy 
+F {#parent-proxy-f}
+:    connection open failed
 
- **s** _server-conn-info_  origin server connection status
+S {#parent-proxy-s}
+:    connection opened successfully
 
- F 
-:    connection open failed 
+blank {#parent-proxy-blank}
+:    no parent proxy
 
- S 
-:    connection opened successfully 
+**s** _server-conn-info_  origin server connection status {#server-conn-info}
 
- blank 
-:    no server connection 
+F {#server-conn-info-f}
+:    connection open failed
 
-###  Support for HTTP Expect: Header  ### {#SupportforHTTPExpectHeader}
+S {#server-conn-info-s}
+:    connection opened successfully
 
-Traffic Server currently does not handle request Expect: headers according to the HTTP/1.1 spec. 
+blank {#server-conn-info-blank}
+:    no server connection
+
+##  Support for HTTP Expect: Header  ## {#SupportforHTTPExpectHeader}
+
+Traffic Server currently does not handle request Expect: headers according to the HTTP/1.1 spec.
 
  Note that clients such as cURL automatically send Expect: for POST requests with large POST bodies, with a 1 second timeout if a 100 Continue response is not received. To avoid the timeout when using cURL as a client to Traffic Server, you can turn off the Expect: header as follows:
 
-command line:     
+command line:
 
     curl -H"Expect:" http://www.example.com/
-    
 
-C (libcurl):     
 
+C (libcurl):
+
+    :::c
     struct curl_slist *header_list=NULL;
-    header_list = curl_slist_append(header_list, "Expect:"); 
-    curl_easy_setopt(my_curlp, CURLOPT_HTTPHEADER, header_list); 
-    
+    header_list = curl_slist_append(header_list, "Expect:");
+    curl_easy_setopt(my_curlp, CURLOPT_HTTPHEADER, header_list);
+
+
+php:
 
-php:     
+    :::php
+    curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
 
-    curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:')); 
-    
 
 
 # Troubleshooting Tips # {#trouble-shooting}
 
 
-### The throughput statistic is inaccurate ### {#throughputstatisticisinaccurate}
+## The throughput statistic is inaccurate ## {#throughputstatisticisinaccurate}
 
-Traffic Server updates the throughput statistic after it has transferred an 
-entire object. For larger files, the byte count increases sharply at the end 
-of a transfer. The complete number of bytes transferred is attributed to the 
-last 10-second interval, although it can take several minutes to transfer the 
-object. This inaccuracy is more noticeable with a light load. A heavier load 
+Traffic Server updates the throughput statistic after it has transferred an
+entire object. For larger files, the byte count increases sharply at the end
+of a transfer. The complete number of bytes transferred is attributed to the
+last 10-second interval, although it can take several minutes to transfer the
+object. This inaccuracy is more noticeable with a light load. A heavier load
 yields a more accurate statistic.
 
-### You are unable to execute Traffic Line commands ### {#YouareunableexecuteTrafficLinecommands}
+## You are unable to execute Traffic Line commands ## {#YouareunableexecuteTrafficLinecommands}
 
-_
 
  Traffic Line commands do not execute under the following conditions:
 
-* **When the `traffic_manager` process is not running**  
- Check to see if the `**traffic_manager**` process is running by entering the following command:   
-` ps aux | grep traffic_manager `  
-  
- If the `traffic_manager` process is not running, then enter the following command from the Traffic Server `bin` directory to start it:  
-`./traffic_manager`   
-  
- You should always start and stop Traffic Server with the `start_traffic_server `and `stop_traffic_server` commands to ensure that all the processes start and stop correctly. For more information, refer to [Getting Started](getstart.htm). 
-* 
-* **When you are not executing the command from `$TSHome/bin`**   
- If the Traffic Server `bin` directory is not in your path, then prepend the Traffic Line commands with `./` (for example, `./traffic_line -h`). 
-* 
-* ** When multiple Traffic Server installations are present and you are not executing the Traffic Line command from the active Traffic Server path specified in `/etc/traffic_server`**``  
- Always switch to the correct directory by issuing the command:  
-`cd `cat /etc/traffic_server`/bin`   
-
-_
-
-### You observe inconsistent behavior when one node obtains an object from another node in the cluster ### {#Youobserveinconsistentbehaviorwhenonenodeobtainsanobjectfromanothernodeincluster}
-
-_
-
-As part of the initial system preparation, you must synchronize the clocks 
-on all nodes in your cluster. Minor time differences do not cause problems, 
-but differences of more than a few minutes can affect Traffic Server operation. 
- 
-
- You should run a clock synchronization daemon such as     
-      xntpd. To obtain the latest version of     
-      xntpd, go to `http://www.eecis.udel.edu/~ntp/`  
-
-_
-
-### Web browsers display an error document with a 'data missing' message ### {#Webbrowsersdisplayanerrordocumentwithadatamissingmessage}
-
-_ A message similar to the following might display in web browsers: 
-
->     
->       Data Missing    
->     
+* **When the `traffic_manager` process is not running**
+ Check to see if the `**traffic_manager**` process is running by entering the following command:
+` ps aux | grep traffic_manager `
+
+ If the `traffic_manager` process is not running, then enter the following command from the Traffic Server `bin` directory to start it:
+`./traffic_manager`
+
+ You should always start and stop Traffic Server with the `start_traffic_server `and `stop_traffic_server` commands to ensure that all the processes start and stop correctly. For more information, refer to [Getting Started](getstart.htm).
+*
+* **When you are not executing the command from `$TSHome/bin`**
+ If the Traffic Server `bin` directory is not in your path, then prepend the Traffic Line commands with `./` (for example, `./traffic_line -h`).
+*
+* ** When multiple Traffic Server installations are present and you are not executing the Traffic Line command from the active Traffic Server path specified in `/etc/traffic_server`**
+
+
+## You observe inconsistent behavior when one node obtains an object from another node in the cluster ## {#Youobserveinconsistentbehaviorwhenonenodeobtainsanobjectfromanothernodeincluster}
+
+
+As part of the initial system preparation, you must synchronize the clocks
+on all nodes in your cluster. Minor time differences do not cause problems,
+but differences of more than a few minutes can affect Traffic Server operation.
+
+
+ You should run a clock synchronization daemon such as
+      xntpd. To obtain the latest version of
+      xntpd, go to `http://www.eecis.udel.edu/~ntp/`
+
+
+## Web browsers display an error document with a 'data missing' message ## {#Webbrowsersdisplayanerrordocumentwithadatamissingmessage}
+
+A message similar to the following might display in web browsers:
+
+>
+>       Data Missing
+>
 >     This document resulted from a POST operation and has expired from the cache. You can repost the form data to recreate the document by pressing the Reload button.
 
- This is a Web browser issue and not a problem specific to (or caused by) Traffic 
-Server. Because Web browsers maintain a separate local cache in memory and/or 
-disk on the client system, messages about documents that have expired from 
-cache refer to the browser's local cache and _not _ to the Traffic Server cache. 
-There is no Traffic Server message or condition that can cause such messages 
-to appear in a web browser. 
-
-_
-
-### Traffic Server does not resolve any websites  ### {#TSdoesnotresolveanywebsites}
-
-_
-
-The browser indicates that it is contacting the host and then times out with 
-the following message: 
-
-> 
->   
-> 
->         
+ This is a Web browser issue and not a problem specific to (or caused by) Traffic
+Server. Because Web browsers maintain a separate local cache in memory and/or
+disk on the client system, messages about documents that have expired from
+cache refer to the browser's local cache and _not _ to the Traffic Server cache.
+There is no Traffic Server message or condition that can cause such messages
+to appear in a web browser.
+
+
+## Traffic Server does not resolve any websites  ## {#TSdoesnotresolveanywebsites}
+
+The browser indicates that it is contacting the host and then times out with
+the following message:
+
+>
+>
+>
+>
 >         The document contains no data; Try again later, or contact the server's Administrator...
->   
-> 
+>
+>
 
- Make sure the system is configured correctly and that Traffic Server can read 
-the name resolution file: 
+ Make sure the system is configured correctly and that Traffic Server can read
+the name resolution file:
 
-* Check if the server can resolve DNS lookups by issuing the     
+* Check if the server can resolve DNS lookups by issuing the
                 nslookup command (for example, `nslookup www.myhost.com`).
 *  Check if the `/etc/resolv.conf` file contains valid IP addresses for your DNS servers.
-*  On some systems, if the `/etc/resolv.conf` file is unreadable or has no name server entry, then the operating system uses `localhost` as a name server. Traffic Server, however, does not use this convention. If you want to use `localhost` as a name server, then you must add a name server entry for `127.0.0.1` or `0.0.0.0` in the `/etc/resolv.conf` file. 
-*  Check that the Traffic Server user account has permission to read the     
+*  On some systems, if the `/etc/resolv.conf` file is unreadable or has no name server entry, then the operating system uses `localhost` as a name server. Traffic Server, however, does not use this convention. If you want to use `localhost` as a name server, then you must add a name server entry for `127.0.0.1` or `0.0.0.0` in the `/etc/resolv.conf` file.
+*  Check that the Traffic Server user account has permission to read the
           /etc/resolv.conf file. If it does not, then change the file permissions to `rw-r--r--` (`644`)
 
-_
 
-### 'Maximum document size exceeded' message in the system log file ### {#Maximumdocumentsizeexceededmessageinsystemlogfile}
+## 'Maximum document size exceeded' message in the system log file ## {#Maximumdocumentsizeexceededmessageinsystemlogfile}
 
-_
 
-The following message appears in the system log file: 
+The following message appears in the system log file:
 
-> 
->   
-> 
->         
->         WARNING: Maximum document size exceeded
->   
-> 
+         WARNING: Maximum document size exceeded
 
- A requested object was larger than the maximum size allowed in the Traffic Server cache, so Traffic Server provided proxy service for the oversized object but did not cache it. To set the object size limit for the cache, modify the     
-      proxy.config.cache.limits.http.max_doc_size variable in the     
+ A requested object was larger than the maximum size allowed in the Traffic Server cache, so Traffic Server provided proxy service for the oversized object but did not cache it. To set the object size limit for the cache, modify the
+      proxy.config.cache.limits.http.max_doc_size variable in the
       records.config file. If you do not want to limit the size of objects in the cache, then set the document size to` **0**`(zero).
 
-_
 
-### 'DrainIncomingChannel' message in the system log file  ### {#DrainIncomingChannelmessageinsystemlogfile}
+## 'DrainIncomingChannel' message in the system log file  ## {#DrainIncomingChannelmessageinsystemlogfile}
 
-_
 
-The following messages may appear in the system log file: 
+The following messages may appear in the system log file:
 
-> 
->   
-> 
->     `Feb 20 23:53:40 louis traffic_manager[4414]: ERROR ==>`
->   
-> 
->   
-> 
->     `[drainIncomingChannel] Unknown message: 'GET http://www.telechamada.pt/`
->   
-> 
->   
-> 
->     `HTTP/1.0'`
-> 
->   
-> 
->     `Feb 20 23:53:46 louis last message repeated 1 time`
-> 
->   
-> 
->     `Feb 20 23:53:58 louis traffic_manager[4414]: ERROR ==>`
->   
-> 
->   
-> 
->     `[drainIncomingChannel] Unknown message: 'GET http://www.ip.pt/ HTTP/1.0'`
->   
-> 
-
- These error messages indicate that a browser is sending HTTP requests to one 
-of the Traffic Server cluster ports - either `rsport` (default port 8088) or 
-`mcport` (default port 8089). Traffic Server discards the request; this error 
-does not cause any Traffic Server problems. The misconfigured browser must 
-be reconfigured to use the correct proxy port. Traffic Server clusters work 
-best when configured to use a separate network interface and cluster on a private 
-subnet, so that client machines have no access to the cluster ports. 
-
-_
-
-### 'No cop file' message in the system log file ### {#Nocopfilemessageinsystemlogfile}
-
-_
-
-The following message appears repeatedly in the system log file: 
-
-> 
->   
-> 
->     `traffic_cop[16056]: encountered "config/internal/no_cop" file...exiting`
->   
-> 
-
- The file `config/internal/no_cop` acts as an administrative control that instructs the `traffic_cop` process to exit immediately without starting `traffic_manager` or performing any health checks. The `no_cop` file prevents Traffic Server from starting automatically when it has been stopped with the `stop_traffic_server` command. Without this static control, Traffic Server would restart automatically upon system reboot. The `no_cop` control keeps Traffic Server off until it is explicitly restarted with the     
-    start_traffic_server command.
-
- The Traffic Server installation script also creates a     
-      no_cop file so that Traffic Server does not start automatically. After you have completed installation/configuration and have rebooted the operating system, use the     
-      start_traffic_server command to start Traffic Server.
+     Feb 20 23:53:40 louis traffic_manager[4414]: ERROR ==> [drainIncomingChannel] Unknown message: 'GET http://www.telechamada.pt/ HTTP/1.0'
+     Feb 20 23:53:46 louis last message repeated 1 time 
+     Feb 20 23:53:58 louis traffic_manager[4414]: ERROR ==> [drainIncomingChannel] Unknown message: 'GET http://www.ip.pt/ HTTP/1.0'
 
-_
+ These error messages indicate that a browser is sending HTTP requests to one
+of the Traffic Server cluster ports - either `rsport` (default port 8088) or
+`mcport` (default port 8089). Traffic Server discards the request; this error
+does not cause any Traffic Server problems. The misconfigured browser must
+be reconfigured to use the correct proxy port. Traffic Server clusters work
+best when configured to use a separate network interface and cluster on a private
+subnet, so that client machines have no access to the cluster ports.
 
-### Warning in the system log file when manually editing `vaddrs.config ` ### {#Warninginsystemlogfilewhenmanuallyediting`vaddrs.config`}
 
-_
+## 'No cop file' message in the system log file ## {#Nocopfilemessageinsystemlogfile}
 
- If you manually edit the     
-      vaddrs.config file as a non-root user, then Traffic Server issues a warning message in the system log file similar to the following:
 
-> 
->   
-> 
->         
->         WARNING: interface is ignored: Operation not permitted
->   
-> 
+The following message appears repeatedly in the system log file:
+
+     traffic_cop[16056]: encountered "config/internal/no_cop" file...exiting
+
+The file `config/internal/no_cop` acts as an administrative control that instructs the `traffic_cop`
+process to exit immediately without starting `traffic_manager` or performing any health checks.
+The `no_cop` file prevents Traffic Server from starting automatically when it has been stopped
+with the `stop_traffic_server` command. Without this static control, Traffic Server would restart
+automatically upon system reboot. The `no_cop` control keeps Traffic Server off until it is explicitly
+restarted with the
 
- You can safely ignore this message; Traffic Server _does_ apply your configuration 
-edits. 
+    start_traffic_server
 
-_
+command.
 
-### Nontransparent requests fail after enabling `always_query_destination` ### {#Nontransparentrequestsfailafterenabling`alwaysquerydestination`}
+The Traffic Server installation script also creates a no_cop file so that Traffic Server does not
+start automatically. After you have completed installation/configuration and have rebooted the
+operating system, use the
 
-_
+      start_traffic_server
 
- The variable     
-      proxy.config.arm.always_query_dest  in the     
-      records.config file configures Traffic Server in transparent mode to ignore host headers and always ask for the IP address of the origin server. When you enable this variable, Traffic Server obtains the origin server IP address from the existing NAT map list rather than trying to resolve the destination hostname with a DNS lookup. As a result, logged URLs contain only IP addresses and no hostnames. However, explicit requests (nontransparent requests, including requests on port 80) fail, as there is no matching map in the NAT list. The `always_query_destination` option works only on the primary proxy port.
+command to start Traffic Server.
 
-_
 
-### Traffic Server is running but no log files are created ### {#TSisrunningbutnologfilesarecreated}
+## Warning in the system log file when manually editing vaddrs.config ## {#Warninginsystemlogfilewhenmanuallyediting}
 
-_
+ If you manually edit the
+      vaddrs.config file as a non-root user, then Traffic Server issues a warning message in the system log file similar to the following:
+
+         WARNING: interface is ignored: Operation not permitted
+
+You can safely ignore this message; Traffic Server _does_ apply your configuration edits.
+
+
+## Traffic Server is running but no log files are created ## {#TSisrunningbutnologfilesarecreated}
 
-Traffic Server only writes event log files when there is information to record. 
-If Traffic Server is idle, then it's possible/probable that no log files exist. 
-In addition: 
+Traffic Server only writes event log files when there is information to record.
+If Traffic Server is idle, then it's possible/probable that no log files exist.
+In addition:
 
-Make sure you're looking in the correct directory. By default, Traffic Server creates log files in the     
-      logs directory. 
-Check the location of log files by checking the value of the variable     
-      proxy.config.log.logfile_dir  in the     
-      records.config file. Check that the log directory has read/write permissions for the Traffic Server user account. If the log directory does not have the correct permissions, then the     
+Make sure you're looking in the correct directory. By default, Traffic Server creates log files in the
+logs directory.
+Check the location of log files by checking the value of the variable
+      proxy.config.log.logfile_dir  in the
+      records.config file. Check that the log directory has read/write permissions for the Traffic Server user account. If the log directory does not have the correct permissions, then the
       traffic_server process is unable to open or create log files.
-Check that logging is enabled by checking the value of the     
-      proxy.config.log.logging_enabled variable in the     
-      records.config file. 
-Check that a log format is enabled. In the     
-      records.config file, select the standard or custom format by editing variables in the     
+Check that logging is enabled by checking the value of the
+      proxy.config.log.logging_enabled variable in the
+      records.config file.
+Check that a log format is enabled. In the
+      records.config file, select the standard or custom format by editing variables in the
       Logging Config section.
-_
 
-### Traffic Server shows an error indicating too many network connections ### {#TSshowsanerrorindicatingtoomanynetworkconnections}
+## Traffic Server shows an error indicating too many network connections ## {#TSshowsanerrorindicatingtoomanynetworkconnections}
 
-_
 
- By default, Traffic Server supports 8000 network connections: half of this 
-number is allocated for client connections and the remaining half is for origin 
-server connections. A **connection throttle event** occurs when client or origin 
-server connections reach 90% of half the configured limit (3600 by default). 
-When a connection throttle event occurs, Traffic Server continues processing 
-all existing connections but will not accept new client connection requests 
-until the connection count falls below the limit. 
+ By default, Traffic Server supports 8000 network connections: half of this
+number is allocated for client connections and the remaining half is for origin
+server connections. A **connection throttle event** occurs when client or origin
+server connections reach 90% of half the configured limit (3600 by default).
+When a connection throttle event occurs, Traffic Server continues processing
+all existing connections but will not accept new client connection requests
+until the connection count falls below the limit.
 
  Connection throttle events can occur under the following conditions:
 
 *  If there is a **connection spike** (e.g., if thousands of client requests all reach Traffic Server at the same time). Such events are typically transient and require no corrective action.
 *  If there is a **service overload** (e.g., if client requests continuously arrive faster than Traffic Server can service them). Service overloads often indicate network problems between Traffic Server and origin servers. Conversely, it may indicate that Traffic Server needs more memory, CPU, cache disks, or other resources to handle the client load.
 
- If necessary, you can reset the maximum number of connections supported by Traffic Server by editing the value of the `_proxy.config.net.connections_throttle _` configuration variable in the     
+ If necessary, you can reset the maximum number of connections supported by Traffic Server by editing the value of the `_proxy.config.net.connections_throttle _` configuration variable in the
     records.config file. Do not increase the connection throttle limit unless the system has adequate memory to handle the client connections required. A system with limited RAM might need a throttle limit lower than the default value. Do not set this variable below the minimum value of 100.
 
-_
 
-### Low memory symptoms ### {#Lowmemorysymptoms}
+## Low memory symptoms ## {#Lowmemorysymptoms}
 
-_
 
-Under heavy load, the Linux kernel can run out of RAM. This low memory condition 
-can cause slow performance and a variety of other system problems. In fact, 
-RAM exhaustion can occur even if the system has plenty of free swap space. 
- 
+Under heavy load, the Linux kernel can run out of RAM. This low memory condition
+can cause slow performance and a variety of other system problems. In fact,
+RAM exhaustion can occur even if the system has plenty of free swap space.
 
- Symptoms of extreme memory exhaustion include the following messages in the 
+
+ Symptoms of extreme memory exhaustion include the following messages in the
 system log files (`/var/log/messages`):
 
-> 
->   
-> 
->     `WARNING: errno 105 is ENOBUFS (low on kernel memory), consider a memory upgrade`
->   
-> 
->   
-> 
->     `kernel: eth0: can't fill rx buffer (force 0)!`
->   
-> 
->   
-> 
->     `kernel: recvmsg bug: copied E01BA916 seq E01BAB22`
->   
-> 
+     WARNING: errno 105 is ENOBUFS (low on kernel memory), consider a memory upgrade `kernel: eth0: can't fill rx buffer (force 0)!
+     kernel: recvmsg bug: copied E01BA916 seq E01BAB22
 
- To avoid memory exhaustion, add more RAM to the system or reduce the load 
+To avoid memory exhaustion, add more RAM to the system or reduce the load
 on Traffic Server.
 
-_
 
-### Connection timeouts with the origin server ### {#Connectiontimeoutswithoriginserver}
+## Connection timeouts with the origin server ## {#Connectiontimeoutswithoriginserver}
 
-_
 
-Certain origin servers take longer than 30 seconds to post HTTP requests, which results in connection timeouts with Traffic Server. To prevent such connection timeouts, you must change the value of the configuration variable     
-      proxy.config.http.connect_attempts_timeout  in the    
+Certain origin servers take longer than 30 seconds to post HTTP requests, which results in connection timeouts with Traffic Server. To prevent such connection timeouts, you must change the value of the configuration variable
+      proxy.config.http.connect_attempts_timeout  in the
       records.config file to 60 seconds or more.
 
-_
-
-### IBM Web servers do not work with Traffic Server ### {#IBMWebserversdonotworkwithTS}
-
-_
-
- IBM web servers do not support the TLS (Transport Layer Security) protocol. 
-For IBM web servers to work with Traffic Server, you must edit a configuration 
-variable. 
-
-#### To configure Traffic Server to work with IBM web servers: #### {#configureTSworkwithIBMwebservers}
-
-1.  In a text editor, open the `records.config` file located in the Traffic Server `config` directory.
-2.  Edit the following configuration variable:   
-**
-                  
- Variable
-                ** **
-                  
- Description
-                ** 
-                  
-_
-                  `proxy.config.ssl.TLSv1`_
-                
-:   
-                          
-        
-         Set this variable to `**0**` (zero).
-        
-        
-                        
-
-3.  Save and close the     
-                records.config file.
-4.  Navigate to the Traffic Server `bin` directory. 
-5.  Run the command     
-                traffic_line -x  to apply the configuration changes._  _  
-

Modified: trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/squid-format.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/squid-format.en.mdtext?rev=1215072&r1=1215071&r2=1215072&view=diff
==============================================================================
--- trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/squid-format.en.mdtext (original)
+++ trafficserver/site/branches/ats-cms/content/docs/trunk/admin/working-log-files/squid-format.en.mdtext Fri Dec 16 09:36:42 2011
@@ -78,3 +78,74 @@ The following list describes each field.
 :   `psct`
 :   The proxy response content type; the object content type taken from the Traffic 
     Server response header.
+
+
+# Squid- and Netscape-format: Cache Result Codes # {#squid-netscape-result-codes}
+
+The following table describes the cache result codes in Squid and Netscape 
+log files.
+
+`TCP_HIT`
+:   A valid copy of the requested object was in the cache and Traffic Server sent the object to the client. 
+
+`TCP_MISS`
+:   The requested object was not in cache, so Traffic Server retrieved the object 
+    from the origin server (or a parent proxy) and sent it to the client.
+
+`TCP_REFRESH_HIT `
+:   The object was in the cache, but it was stale. Traffic Server made an
+    * `if-modified-since` request to the origin server and the origin server sent a
+    * `304` not-modified response. Traffic Server sent the cached object to the client.
+ 
+`TCP_REF_FAIL_HIT`
+:   The object was in the cache but was stale. Traffic Server made an
+    * `if-modified-since` request to the origin server but the server did not respond. Traffic Server sent the cached object to the client.
+
+`TCP_REFRESH_MISS`
+:   The object was in the cache but was stale. Traffic Server made an
+    * `if-modified-since` request to the origin server and the server returned a new object. Traffic Server served the new object to the client.
+
+`TCP_CLIENT_REFRESH`
+:   The client issued a request with a `no-cache` header. Traffic Server obtained 
+    the requested object from the origin server and sent a copy to the client. 
+    Traffic Server deleted the previous copy of the object from cache.
+
+`TCP_IMS_HIT`
+:   The client issued an
+    * `if-modified-since` request and the object was in cache & fresher than the IMS date, **or** an
+    * `if-modified-since` request to the origin server revealed the cached object was fresh.
+    Traffic Server served the cached object to the client.
+
+`TCP_IMS_MISS`
+:   The client issued an     
+    `if-modified-since request`, and the object was either not in cache or was stale in cache. Traffic Server sent an     
+    `if-modified-since request` to the origin server and received the new object. Traffic Server sent the updated object to the client.
+
+`TCP_SWAPFAIL`
+:   The object was in the cache but could not be accessed. The client did not 
+    receive the object.
+
+`ERR_CLIENT_ABORT`
+:   The client disconnected before the complete object was sent.
+
+`ERR_CONNECT_FAIL`
+:   Traffic Server could not reach the origin server.
+
+`ERR_DNS_FAIL`
+:   The Domain Name Server (DNS) could not resolve the origin server name, or 
+    no DNS could be reached.
+
+`ERR_INVALID_REQ`
+:   The client HTTP request was invalid. (Traffic Server forwards requests with 
+    unknown methods to the origin server.) 
+
+`ERR_READ_TIMEOUT`
+:   The origin server did not respond to Traffic Server's request within the timeout 
+    interval.
+
+`ERR_PROXY_DENIED`
+:   Client service was denied.
+
+
+`ERR_UNKNOWN`
+:   The client connected, but subsequently disconnected without sending a request. 



Mime
View raw message