Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/configure.htm
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/configure.htm
(added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/configure.htm
Mon Dec 19 22:58:01 2011
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd";>
+<html>
+<head>
+<title>Traffic Edge Administrator's Guide</title>
+
+<!--#include file="top.html" -->
+
+<h1>Configuring Traffic Server</h1>
+<p>Traffic Server provides several options for configuring the system.</p>
+<p>This chapter discusses the following topics: </p>
+<ul>
+<li><a href="#ConfiguringTrafficEdgeUsingTrafficLine">Configure Traffic Server
Using Traffic Line</a></li>
+<li><a href="#ConfiguringTrafficEdgeUsingConfigFiles">Configure Traffic Server
Using Configuration Files</a></li>
+</ul>
+<h2 id="ConfiguringTrafficEdgeUsingTrafficLine">Configure Traffic Server Using
Traffic Line</h2>
+<p>Traffic Line enables you to quickly and easily change your Traffic Server
configuration via command-line interface. Alternatively, you can also use <a
href="getstart.htm#StartingTrafficShell">Traffic Shell</a> to configure Traffic
Server.</p>
+<h5>To view or change configuration options in Traffic Line: </h5>
+<ol>
+ <li>Log on to a Traffic Server node as the Traffic Server administrator and
navigate to the Traffic Server <code>bin</code> directory. </li>
+ <li>To view a configuration setting, enter the following command: <br
/><code>traffic_line -r <em>var</em></code><br />
+ where <em><code>var</code></em> is the variable associated with the
configuration option. For a list of variables, refer to <a
href="files.htm#config_var">Configuration Variables</a>.</li>
+ <li>To change the value of a configuration setting, enter the following
command:
+ <br /><code>traffic_line -s <em>var</em> -v <em>value</em></code> <br />
+ where <em><code>var</code></em> is the variable associated with the
configuration option and <em><code>value</code></em> is the value you want to
use. For a list of the variables, see <a
href="files.htm#config_var">Configuration Variables</a>.<br /> <br /> If the
Traffic Server <code>bin</code> directory is not in your path, then prepend the
Traffic Line command with <code>./</code> (for example, <code>./traffic_line -r
variable</code>).</li>
+</ol>
+<h2 id="ConfiguringTrafficEdgeUsingConfigFiles">Configure Traffic Server Using
Configuration Files</h2>
+<p>As an alternative to using Traffic Line or Traffic Shell, you can change
Traffic Server configuration options by manually editing specific variables in
the <code>records.config</code> file located in the Traffic Server
<code>config</code> directory. To edit the variables, open the file in a text
editor (such as <code>vi</code> or <code>emacs</code>) and change variable
values. After you modify the <code>records.config</code> file, Traffic Server
must reread the configuration files. From the Traffic Server <code>bin</code>
directory, enter the Traffic Line command <code>traffic_line -x</code>. You
may need to restart Traffic Server to apply the configuration changes. </p>
+<p>The following is a sample portion of the <code>records.config</code> file:
</p>
+<p><img src="images/records.jpg" width="812" height="609" /></p>
+<blockquote>
+ <p><em><b>Sample records.config file </b></em></p>
+</blockquote>
+<p>In addition to the <code>records.config</code> file, Traffic Server
provides other configuration files that are used to configure specific
features. All configuration files you can manually edit are described in <a
href="files.htm">Configuration Files</a>. </p>
+
+<!--#include file="bottom.html" -->
\ No newline at end of file
Propchange:
websites/staging/trafficserver/trunk/content/docs/v2/admin/configure.htm
------------------------------------------------------------------------------
svn:executable = *
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/doc.css
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/doc.css (added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/doc.css Mon Dec
19 22:58:01 2011
@@ -0,0 +1,28 @@
+body{
+ font-family:Tahoma, Geneva, sans-serif;
+ width:95%;
+}
+h1{
+ font-family:Arial;
+}
+h2{border-style: solid none none; border-color: grey; border-width: 3px 0px
0px;font-family:Arial;}
+h3{font-family:Arial;}
+h5{font-family:Arial; padding: 5px 5px 5px 15px;
background:url(http://us.i1.yimg.com/us.yimg.com/i/us/pim/bn/downbr1.gif)
no-repeat left center;}
+code{padding:15px 0px;}
+table{border:thin solid;border-collapse:collapse;}
+td{border:thin solid grey; border-top-style:solid;}
+h1.doctitle{
+ position:relative;
+ top:-8px;
+ display:inline;
+ margin-left:10px;
+}
+ul.leftnav{
+ margin-left:0px;
+ padding-left:15px;
+ font-family: Tahoma, Geneva, sans-serif;
+ width:170px;
+}
+#ft #incu_logo{float:right;}
+#cse-search-box{display:inline; float:right;margin:15px 5px 0 5px;}
+img{border:0;}
\ No newline at end of file
Propchange: websites/staging/trafficserver/trunk/content/docs/v2/admin/doc.css
------------------------------------------------------------------------------
svn:executable = *
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/errors.htm
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/errors.htm
(added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/errors.htm Mon
Dec 19 22:58:01 2011
@@ -0,0 +1,409 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd";>
+<html>
+<head>
+<title>Traffic Server Error Messages</title>
+
+<!--#include file="top.html" -->
+
+ <h1><a name="48024">Appendix F - Traffic Server Error Messages</a>
+ </h1>
+<p> This appendix contains the following sections:</p>
+<ul>
+<li><a href="#57301">Traffic Server Error Messages</a>: describes the warning
messages Traffic Server sends to the system log file.</li>
+<li><a href="#65686">Traffic Server Alarm Messages</a>: describes the alarm
messages that may appear on Traffic Manager Monitor pages.</li>
+<li><a href="#55499">HTML Messages Sent to Clients</a>: describes the HTML
error messages Traffic Server sends to browser clients.</li>
+<li><a href="#55388">Standard HTTP Response Messages</a>: describes the
standard HTTP response codes origin servers send to browser clients.</li>
+</ul>
+
+ <h2>
+ <a name="57301">Traffic Server Error Messages</a> </h2>
+<p>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. </p>
+ <h3>
+ <a name="57388">Traffic Server Process Fatal</a> </h3>
+ <table border="1">
+ <tr>
+ <th> <p> Message</p></th>
+ <th> <p> Description</p></th>
+ </tr>
+ <tr>
+ <td><p> <code>Accept port is not between 1 and 65535. Please check
configuration</code></p></td>
+ <td><p> The port specified in the <code> records.config</code> file
that accepts incoming HTTP requests is not valid. </p></td>
+ </tr>
+ <tr>
+ <td><p> <code>Self loop is detected in parent proxy
configuration</code></p></td>
+ <td><p> 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. </p></td>
+ </tr>
+ </table>
+ <h3>
+ <a name="65683">Traffic Server Warnings</a> </h3>
+ <table border="1">
+ <tr>
+ <th> <p> Message</p></th>
+ <th> <p> Description</p></th>
+ </tr>
+ <tr>
+ <td><p> <code><em> Logfile</em> error: <em> error_number</em>
</code></p></td>
+ <td><p> Generic logging error.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Bad cluster major version range <em> version1</em>
-<em> version2</em> for node <em> IP address</em> connect failed</code></p></td>
+ <td><p> Incompatible software versions causing a problem.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Can't open config file <em> filename</em> for reading
custom formats</code></p></td>
+ <td><p> Custom logging is enabled, but Traffic Server cannot find the
<code> logs.config</code> file. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Connect by disallowed client <em> IP address</em>,
closing</code></p></td>
+ <td><p> The specified client is not allowed to connect to Traffic
Server; the client IP address is not listed in the <code>
ip_allow.config</code> file. </p></td>
+ </tr>
+ <tr>
+ <td><p> Could not rename log<em> <code>filename</code></em> to <em>
<code>rolled filename</code></em> </p></td>
+ <td><p> System error when renaming log file during roll. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Did <em> this_amount</em> of backup; still to do <em>
remaining_amount</em> </code></p></td>
+ <td><p> Congestion is approaching.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Different clustering minor versions <em> version1</em>
, <em> version2</em> for node <em> IP address</em> continuing</code></p></td>
+ <td><p> Incompatible software versions are causing a problem.
</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Log format symbol <em> symbol_name</em> not
found</code></p></td>
+ <td><p> Custom log format references a field symbol that does not
exist. Refer to <a href="logfmts.htm">Event Logging Formats</a>.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Missing field for field marker</code></p></td>
+ <td><p> Error reading a log buffer.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Unable to open log file<em> filename</em>, errno=<em>
error_number</em> </code></p></td>
+ <td><p> Cannot open the log file.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Error accessing disk <em> disk_name</em>
</code></p></td>
+ <td><p> Traffic Server might have a cache read problem. You might
need to replace the disk.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> Too many errors accessing disk <em> disk_name</em> :
declaring disk bad</code></p></td>
+ <td><p> 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.</p></td>
+ </tr>
+ <tr>
+ <td><p><code> No cache disks specified in storage.config file: cache
disabled</code></p></td>
+ <td><p> The Traffic Server <code> storage.config</code> 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 <a
href="files.htm#storage.config">storage.config</a> file.</p></td>
+ </tr>
+ </table>
+ <h2>
+<a name="65686">Traffic Server Alarm Messages</a></h2>
+ <p> </p>
+ <table border="1">
+ <tr>
+ <th> <p> Message</p></th>
+ <th> <p> Description</p></th>
+ </tr>
+ <tr>
+ <td><p><code> [Rollback::Rollback] Config file is read-only:<em>
filename</em></code></p></td>
+ <td><p> Go to the Traffic Server <code> config</code> directory and
check the indicated file permissions; change if necessary. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> [Rollback::Rollback] Unable to read or write config
file<em> filename</em></code></p></td>
+ <td><p> Go to the Traffic Server <code> config</code> directory and
make sure the indicated file exists. Check permissions and modify if
necessary. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> [Traffic Manager] Configuration File Update Failed:
<em> error_number</em> </code></p></td>
+ <td><p> Go to the Traffic Server <code> config</code> directory and
check the indicated file permissions; change if necessary. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> [Traffic Manager] Mgmt <==>Proxy conn.
closed</code></p></td>
+ <td><p> An informational message to inform you that the <code>
traffic_server</code> process is down. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Access logging suspended - configured space allocation
exhausted. </code></p></td>
+ <td><p> 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. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Access logging suspended - no more space on the logging
partition.</code></p></td>
+ <td><p> 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. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Created zero length place holder for config file<em>
filename</em> </code></p></td>
+ <td><p> Go to the Traffic Server <code> config</code> directory and
check the indicated file. If it is indeed zero in length, then use a backup
copy of the configuration file. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Traffic Server can't open<em> filename </em>for reading
custom formats</code></p></td>
+ <td><p> Make sure the <code>
<i>proxy.config.log.config_file</i></code> variable in the <code>
records.config</code> file contains the correct path to the custom log
configuration file (the default is<code> logging/logs.config</code> ). </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Traffic Server could not open logfile <em>
filename</em> </code></p></td>
+ <td><p> Check permissions for the indicated file and the logging
directory. </p></td>
+ </tr>
+ <tr>
+ <td><p><code> Traffic Server failed to parse line <em>
line_number</em> of the logging config file<em> filename</em></code></p></td>
+ <td><p> Check your custom log configuration file; there could be
syntax errors. Refer to <a href="logfmts.htm#66912"> Custom Logging Fields</a>
for correct custom log format fields. </p></td>
+ </tr>
+ <tr>
+ <td><p> <code>vip_config binary is not setuid root, manager will be
unable to enable virtual ip addresses</code></p></td>
+ <td><p> The <code> traffic_manager</code> process is not able to set
virtual IP addresses. You must <code>setuid root </code>for the <code>
vip_config</code> file in the Traffic Server <code> bin</code> directory.
</p></td>
+ </tr>
+ </table>
+ <h2>
+ <a name="55499">HTML Messages Sent to Clients</a> </h2>
+<p>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 <a href="#55388">Standard HTTP Response
Messages</a>. You can customize the Traffic Server response messages, if
desired.</p>
+<p>The following table lists the hard-coded Traffic Server HTTP messages,
with corresponding HTTP response codes and customizable files. </p>
+ <table border="1">
+ <tr>
+ <th> <p> Title </p></th>
+ <th> <p> HTTP Code</p></th>
+ <th> <p> Description</p></th>
+ <th> <p> Customizable Filename</p></th>
+ </tr>
+ <tr>
+ <td><p><code> Access Denied</code></p></td>
+ <td><p><code> 403</code></p></td>
+ <td><p> You are not allowed to access the document at location
<code><em> URL</em></code> . </p></td>
+ <td><p><code> access#denied</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Cache Read Error</code></p></td>
+ <td><p><code> 500</code></p></td>
+ <td><p> Error reading from cache; please retry request.</p></td>
+ <td><p><code> cache#read_error</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Connection Timed Out</code></p></td>
+ <td><p><code> 504</code></p></td>
+ <td><p> Too much time has elapsed since the server has sent data.
</p></td>
+ <td><p><code> timeout#inactivity</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Content Length Required</code></p></td>
+ <td><p><code> 400</code></p></td>
+ <td><p> Could not process this request because
<code>Content-Length</code> was not specified.</p></td>
+ <td><p><code> request#no_content_length</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Cycle Detected</code></p></td>
+ <td><p><code> 400</code></p></td>
+ <td><p> Your request is prohibited because it would cause an HTTP
proxy cycle. </p></td>
+ <td><p><code> request#cycle_detected</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Forbidden</code></p></td>
+ <td><p><code> 403</code></p></td>
+ <td><p> <code><em> port_number</em></code> is not an allowed port
for SSL connections (you have made a request for a secure SSL connection to a
forbidden port number).</p></td>
+ <td><p><code> access#ssl_forbidden</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Host Header Required</code></p></td>
+ <td><p><code> 400</code></p></td>
+ <td><p> An attempt was made to transparently proxy your request, but
this attempt failed because your browser did not send an HTTP <code>
Host</code> header. Manually configure your browser to use <code>
http://</code> <code><em> proxy_name</em></code> :<code><em>
proxy_port</em></code> as the HTTP proxy. Alternatively, end users can upgrade
to a browser that supports the HTTP <code> Host</code> header field.</p></td>
+ <td><p><code> interception#no_host</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Host Header Required</code></p></td>
+ <td><p><code> 400</code></p></td>
+ <td><p> Because your browser did not send a <code>Host</code> 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 <code>Host</code> header field.</p></td>
+ <td><p><code> request#no_host</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> HTTP Version Not Supported</code></p></td>
+ <td><p><code> 505</code></p></td>
+ <td><p> The origin server <em><code> server_name</code></em> is
using an unsupported version of the HTTP protocol.</p></td>
+ <td><p><code> response#bad_version</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Invalid HTTP Request</code></p></td>
+ <td><p><code> 400</code></p></td>
+ <td><p> Could not process this <code><em> client_request</em></code>
HTTP method request for <em><code> URL</code></em> .</p></td>
+ <td><p><code> request#syntax_error</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Invalid HTTP Response</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p> The host <code><em> server_name</em></code> did not return
the document <code><em> URL</em></code> correctly.</p></td>
+ <td><p><code> response#bad_response</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Malformed Server Response</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p> The host <code><em> server_name</em></code> did not return
the document <code><em> URL</em></code> correctly.</p></td>
+ <td><p><code> response#bad_response</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Malformed Server Response Status</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p> The host <code><em> server_name </em></code> did not return
the document <code><em> URL </em></code> correctly.</p></td>
+ <td><p><code> response#bad_response</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Maximum Transaction Time exceeded</code></p></td>
+ <td><p><code> 504</code></p></td>
+ <td><p> Too much time has elapased while transmitting document
<code><em> URL</em></code> .</p></td>
+ <td><p><code> timeout#activity</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> No Response Header From Server</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p align="left"> The host <code><em> server_name </em></code>
did not return the document <code><em> URL</em></code> correctly.</p></td>
+ <td><p><code> response#bad_response</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Not Cached</code></p></td>
+ <td><p><code> 504</code></p></td>
+ <td><p> This document was not available in the cache, and you (the
client) only accept cached copies.</p></td>
+ <td><p><code> cache#not_in_cache</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Not Found on Accelerator</code></p></td>
+ <td><p><code> 404</code></p></td>
+ <td><p> The request for <code><em> URL</em></code> on host
<code><em> server_name </em></code> was not found. Check the location and try
again.</p></td>
+ <td><p><code> urlrouting#no_mapping</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> NULL</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p> The host <code><em> hostname</em></code> did not return the
document <code><em> URL</em></code> correctly.</p></td>
+ <td><p><code> response#bad_response</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Proxy Authentication Required</code></p></td>
+ <td><p><code> 407</code></p></td>
+ <td><p> Please log in with username and password.</p></td>
+ <td><p><code> access#proxy_auth_required</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Server Hangup</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p> The server <code><em> hostname</em></code> closed the
connection before the transaction was completed.</p></td>
+ <td><p><code> connect#hangup</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Temporarily Moved</code></p></td>
+ <td><p><code> 302</code></p></td>
+ <td><p> The document you requested,<code><em> URL</em></code> , has
moved to a new location. The new location is <code><em> new_URL</em></code>
.</p></td>
+ <td><p><code> redirect#moved_temporarily</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Transcoding Not Available</code></p></td>
+ <td><p><code> 406</code></p></td>
+ <td><p> Unable to provide the document <code><em> URL</em></code> in
the format requested by your browser.</p></td>
+ <td><p><code> transcoding#unsupported</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Tunnel Connection Failed</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p> Could not connect to the server <code><em>
hostname</em></code> .</p></td>
+ <td><p><code> connect#failed_connect</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Unknown Error</code></p></td>
+ <td><p><code> 502</code></p></td>
+ <td><p> The host <code><em> hostname</em></code> did not return the
document <code><em> URL</em></code> correctly.</p></td>
+ <td><p><code> response#bad_response</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Unknown Host</code></p></td>
+ <td><p><code> 500</code></p></td>
+ <td><p> Unable to locate the server named <code><em>
hostname</em></code>; 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. </p></td>
+ <td><p><code> connect#dns_failed</code></p></td>
+ </tr>
+ <tr>
+ <td><p><code> Unsupported URL Scheme</code></p></td>
+ <td><p><code> 400</code></p></td>
+ <td><p> Cannot perform your request for the document <code><em>
URL</em></code> because the protocol scheme is unknown.</p></td>
+ <td><p><code> request#scheme_unsupported</code></p></td>
+ </tr>
+ </table>
+ <h3>
+ <a name="55388">Standard HTTP Response Messages </a> </h3>
+<p>The following standard HTTP response messages are provided for your
information. </p>
+
+ <table border="1">
+ <tr>
+ <th> <p> Message</p></th>
+ <th> <p> Description</p></th>
+ </tr>
+ <tr>
+ <td><p><strong><code> 200</code></strong></p></td>
+ <td><p> OK</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 202</code></strong></p></td>
+ <td><p> Accepted</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 204</code></strong></p></td>
+ <td><p> No Content</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 206</code></strong></p></td>
+ <td><p> Partial Content</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 300 </code></strong></p></td>
+ <td><p> Multiple Choices</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 301</code></strong></p></td>
+ <td><p> Moved Permanently</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 302</code></strong></p></td>
+ <td><p> Found</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 303</code></strong></p></td>
+ <td><p> See Other</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 304</code></strong></p></td>
+ <td><p> Not Modified</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 400</code></strong></p></td>
+ <td><p> Bad Request</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 401</code></strong></p></td>
+ <td><p> Unauthorized; retry</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 403</code></strong></p></td>
+ <td><p> Forbidden</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 404</code></strong></p></td>
+ <td><p> Not Found</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 405</code></strong></p></td>
+ <td><p> Method Not Allowed</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 406</code></strong></p></td>
+ <td><p> Not acceptable</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 408</code></strong></p></td>
+ <td><p> Request Timeout</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 500</code></strong></p></td>
+ <td><p> Internal server error</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 501 </code></strong></p></td>
+ <td><p> Not Implemented</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 502</code></strong></p></td>
+ <td><p> Bad Gateway</p></td>
+ </tr>
+ <tr>
+ <td><p><strong><code> 504</code></strong></p></td>
+ <td><p> Gateway Timeout</p></td>
+ </tr>
+ </table>
+
+<!--#include file="bottom.html" -->
\ No newline at end of file
Propchange:
websites/staging/trafficserver/trunk/content/docs/v2/admin/errors.htm
------------------------------------------------------------------------------
svn:executable = *
Added: websites/staging/trafficserver/trunk/content/docs/v2/admin/explicit.htm
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/v2/admin/explicit.htm
(added)
+++ websites/staging/trafficserver/trunk/content/docs/v2/admin/explicit.htm Mon
Dec 19 22:58:01 2011
@@ -0,0 +1,57 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd";>
+<html>
+<head>
+<title>Traffic Edge Administrator's Guide</title>
+
+<!--#include file="top.html" -->
+
+<h1>Explicit Proxy Caching</h1>
+<p>If you want to use Traffic Server as an explicit proxy cache, you must
configure client software (i.e., browsers) to send requests directly to Traffic
Server.</p>
+<h2 id="ExplicitProxyCachingHTTP">Explicit Proxy Caching for HTTP</h2>
+<p> If you do not configure Traffic Server to use the transparency option
(with which client requests are intercepted en route to origin servers by a
switch/router and rerouted to the Traffic Server machine), then clients must
configure their web browsers to send HTTP requests to the Traffic Server proxy
cache by configuring their browsers to download proxy configuration
instructions from a <a href="#UsingPACFile">PAC file</a> (Proxy
Auto-Configuration file).</p>
+<h3 id="ConfiguringBrowsersManually">Configuring Browsers Manually </h3>
+<p>To manually configure a browser to send HTTP requests to Traffic Server,
clients must provide the following information: </p>
+<ul>
+ <li>The fully-qualified hostname or IP address of the Traffic Server
node</li>
+ <li>The Traffic Server proxy server port (port 8080)</li>
+</ul>
+<p>In addition, clients can specify <i>not</i> to use Traffic Server for
certain sites - in such cases, requests to the listed sites go directly to the
origin server. The procedures for manual configuration vary among browser
versions; refer to specific browser documentation for complete proxy
configuration instructions. You do not need to set any special configuration
options on Traffic Server if you want to accept requests from
manually-configured browsers. </p>
+<h3 id="UsingPACFile">Using a PAC File </h3>
+<p>A <b>PAC file</b> is a specialized JavaScript function definition that a
browser calls to determine how requests are handled. Clients must specify (in
their browser settings) the URL from which the PAC file is loaded. You can
store a PAC file on Traffic Server (or on any server in your network) and then
provide the URL for this file to your clients. </p>
+<p>If you want to store a PAC file on the Traffic Server system, then you must
perform the following configuration: </p>
+<ul>
+ <li>Either copy an existing PAC file into the Traffic Server
<code>config</code> directory or enter a script that defines the proxy server
configuration settings in the <code>proxy.pac</code> file provided (the file is
empty by default). </li>
+ <li>Specify the port Traffic Server uses to serve the PAC file. The default
port is 8083.</li>
+</ul>
+<h5>Configure Traffic Server to provide a PAC file manually: </h5>
+<ol>
+ <li>If you have an existing PAC file, then replace the
<code>proxy.pac</code> file located in the Traffic Server <code>config</code>
directory with the existing file. </li>
+ <li>In a text editor, open the <code>records.config</code> file located in
the Traffic Server <code>config</code> directory. </li>
+ <li>Edit the following variable:</li>
+ <table width="1232" border="1">
+ <tr>
+ <th width="322" scope="col">Variable</th>
+ <th width="894" scope="col">Description</th>
+ </tr>
+ <tr>
+ <td><code><i>proxy.config.admin.autoconf_port</i></code></td>
+ <td><p>Set this variable to specify the port Traffic Server uses to
serve the PAC file. The default port is 8083.</p> </td>
+ </tr>
+</table>
+ <li>Save and close the <code>records.config</code> file. </li>
+ <li>In a text editor, open the <code>proxy.pac</code> file located in the
Traffic Server <code>config</code> directory. </li>
+ <ul>
+ <li>If you copied an existing PAC file into the Traffic Server config
directory, then the <code>proxy.pac</code> file contains your proxy
configuration settings. Check the settings and make changes if necessary. </li>
+ <li>If you did not copy an existing PAC file into the Traffic Server
<code>config</code> directory, then the <code>proxy.pac</code> file is empty.
Enter a script that will provide the proxy server configuration settings. A
sample script is provided in <a href="#SamplePACFile">Sample PAC File</a>. </li>
+</ul>
+<li>Save and close the <code>proxy.pac</code> file. </li>
+ <li>Restart Traffic Server. </li>
+ <li>Inform your users to set their browsers to point to this PAC file; <a
href="#SetBrowsersPointPACFile">click here for browser settings</a>. </li>
+</ol>
+<h4 id="SamplePACFile">Sample PAC File </h4>
+<p>The following sample PAC file instructs browsers to connect directly to all
hosts without a fully-qualified domain name and to all hosts in the local
domain. All other requests go to the Traffic Server named
<code>myproxy.company.com</code>.</p>
+<pre>function FindProxyForURL(url, host) <br />{<br /> if
(isPlainHostName(host)) ||<br /> (localHostOrDomainIs(host,
".company.com")) {<br /> return "DIRECT";<br />
}<br /> else<br /> return "PROXY
myproxy.company.com:8080;" +<br />
"DIRECT"; <br />} </pre>
+<h3 id="UsingWPAD"> </h3>
+<p> </p>
+
+<!--#include file="bottom.html" -->
\ No newline at end of file
Propchange:
websites/staging/trafficserver/trunk/content/docs/v2/admin/explicit.htm
------------------------------------------------------------------------------
svn:executable = *
