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 2012/11/13 21:02:58 UTC
svn commit: r1408925 - in /trafficserver/site/trunk/content/docs/trunk/admin:
configuration-files/records.config.en.mdtext faqs/index.en.mdtext
Author: igalic
Date: Tue Nov 13 20:02:57 2012
New Revision: 1408925
URL: http://svn.apache.org/viewvc?rev=1408925&view=rev
Log:
Link Via decoder ring - it seems the Via docs in records.config is incomplete
Modified:
trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
trafficserver/site/trunk/content/docs/trunk/admin/faqs/index.en.mdtext
Modified: trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext?rev=1408925&r1=1408924&r2=1408925&view=diff
==============================================================================
--- trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext (original)
+++ trafficserver/site/trunk/content/docs/trunk/admin/configuration-files/records.config.en.mdtext Tue Nov 13 20:02:57 2012
@@ -375,7 +375,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)
+ Note: the Via: header string interpretation can be [docoded here.](/tools/via)
*`proxy.config.http.insert_response_via_str`* {#proxy.config.http.insert_response_via_str}
Modified: trafficserver/site/trunk/content/docs/trunk/admin/faqs/index.en.mdtext
URL: http://svn.apache.org/viewvc/trafficserver/site/trunk/content/docs/trunk/admin/faqs/index.en.mdtext?rev=1408925&r1=1408924&r2=1408925&view=diff
==============================================================================
--- trafficserver/site/trunk/content/docs/trunk/admin/faqs/index.en.mdtext (original)
+++ trafficserver/site/trunk/content/docs/trunk/admin/faqs/index.en.mdtext Tue Nov 13 20:02:57 2012
@@ -19,7 +19,7 @@ Navigation: [*](*)
-[TOC]
+#[TOC]
# FAQs # {#FAQs}
@@ -106,237 +106,8 @@ Please refer to the [Forward Proxy](../f
## How do I interpret the Via: header code? ## {#interpret-via}
-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.
+Take a look at our [Via decoder Ring](/tools/via)
-The form of the Via header is
-
- :::text
- Via: <protocol> <proxyname> (<product/version> [<via-codes>]
-
-* _<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
-
-For example:
-
- :::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 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
-
-[[*u<client-info>*](#client-info) [*c<cache-lookup>*](#cache-lookup) [*s<server-info>*](#server-info) [*f<cache-fill>*](#cache-fill) [*p<proxy-info>*](#proxy-info) [*e<error-codes>*](#error-codes) [*:*](#separator) [*t<tunnel-info>*](#tunnel-info)[*c<cache-type>*](#cache-type)[*<cache-lookup-result>*](#cache-lookup-result) [*i<icp-conn-info>*](#icp-conn-info) [*p<parent-proxy>*](#parent-proxy) [*s<server-conn-info>*](#server-conn-info)]
-
-**u** _client-info_ Request headers received from client. Value is one of: {#client-info}
-
-C {#client-info-c}
-: cookie
-
-E {#client-info-e}
-: error in request
-
-I {#client-info-i}
-: If Modified Since (IMS)
-
-N {#client-info-n}
-: no-cache
-
-S {#client-info-s}
-: simple request (not conditional)
-
-**c** _cache-lookup_ Result of Traffic Server cache lookup for URL. Value is one of: {#cache-lookup}
-
-A {#cache-lookup-a}
-: in cache, not acceptable (a cache "MISS")
-
-H {#cache-lookup-h}
-: in cache, fresh (a cache "HIT")
-
-M {#cache-lookup-m}
-: miss (a cache "MISS")
-
-S {#cache-lookup-s}
-: in cache, stale (a cache "MISS")
-
-R {#cache-lookup-r}
-: in cache, fresh Ram hit (a cache "HIT")
-
-blank {#cache-lookup-blank}
-: no cache lookup performed
-
-**s** _server-info_ Response information received from origin server. Value is one of: {#server-info}
-
-E {#server-info-e}
-: error in response
-
-N {#server-info-n}
-: not-modified
-
-S {#server-info-s}
-: served
-
-blank {#server-info-blank}
-: no server connection needed
-
-**f** _cache-fill_ Result of document write to cache. Value is one of: {#cache-fill}
-
-D {#cache-fill-d}
-: cached copy deleted
-
-U {#cache-fill-u}
-: updated old cache copy
-
-W {#cache-fill-w}
-: written into cache (new copy)
-
-blank {#cache-fill-blank}
-: no cache write performed
-
-
-**p** _proxy-info_ Proxy operation result. Value is one of: {#proxy-info}
-
-N {#proxy-info-n}
-: not-modified
-
-R {#proxy-info-r}
-: origin server revalidated
-
-S {#proxy-info-s}
-: served
-
-**e** _error-codes_ Value is one of: {#error-codes}
-
-A {#error-codes-a}
-: authorization failure
-
-C {#error-codes-c}
-: connection to server failed
-
-D {#error-codes-d}
-: dns failure
-
-F {#error-codes-f}
-: request forbidden
-
-H {#error-codes-h}
-: header syntax unacceptable
-
-N {#error-codes-n}
-: no error
-
-S {#error-codes-s}
-: server related error
-
-T {#error-codes-t}
-: connection timed out
-
-**:** = Separates proxy request result information from operation detail codes {#separator}
-
-**t** _tunnel-info_ Proxy-only service operation. Value is one of: {#tunnel-info}
-
-F {#tunnel-info-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)
-
-O {#tunnel-info-o}
-: tunneling because cache is turned off
-
-U {#tunnel-info-u}
-: tunneling because of url (url suggests dynamic content)
-
-blank {#tunnel-info-blank}
-: no tunneling
-
-**c** _cache-type_ and _cache-lookup_ cache result values (2 characters) {#cache-type}
-
-cache-type character value is one of
-
-C {#cache-type-c}
-: cache
-
-I {#cache-type-i}
-: icp
-
-blank {#cache-type-blank}
-: cache miss or no cache lookup
-
-cache-lookup-result character value is one of: {#cache-lookup-result}
-
-C {#cache-lookup-result-c}
-: cache hit, but config forces revalidate
-
-D {#cache-lookup-result-d}
-: cache hit, but method forces revalidated (e.g. ftp, not anonymous)
-
-H {#cache-lookup-result-h}
-: cache hit
-
-I {#cache-lookup-result-i}
-: conditional miss (client sent conditional, fresh in cache, returned 412)
-
-M {#cache-lookup-result-m}
-: cache miss (url not in cache)
-
-N {#cache-lookup-result-n}
-: conditional hit (client sent conditional, doc fresh in cache, returned 304)
-
-S {#cache-lookup-result-s}
-: cache hit, but expired
-
-U {#cache-lookup-result-u}
-: cache hit, but client forces revalidate (e.g. Pragma: no-cache)
-
-blank {#cache-lookup-result-blank}
-: no cache lookup
-
-**i** _icp-conn-info_ ICP status {#icp-conn-info}
-
-F {#icp-conn-info-f}
-: connection open failed
-
-S {#icp-conn-info-s}
-: connection opened successfully
-
-blank {#icp-conn-info-blank}
-: no icp
-
-**p** _parent-proxy_ parent proxy connection status {#parent-proxy}
-
-F {#parent-proxy-f}
-: connection open failed
-
-S {#parent-proxy-s}
-: connection opened successfully
-
-blank {#parent-proxy-blank}
-: no parent proxy
-
-**s** _server-conn-info_ origin server connection status {#server-conn-info}
-
-F {#server-conn-info-f}
-: connection open failed
-
-S {#server-conn-info-s}
-: connection opened successfully
-
-blank {#server-conn-info-blank}
-: no server connection
## Support for HTTP Expect: Header ## {#SupportforHTTPExpectHeader}