trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r849552 - in /websites/staging/trafficserver/trunk: cgi-bin/ content/ content/docs/trunk/admin/configuration-files/records.config.en.html
Date Wed, 06 Feb 2013 07:18:11 GMT
Author: buildbot
Date: Wed Feb  6 07:18:11 2013
New Revision: 849552

Log:
Staging update by buildbot for trafficserver

Modified:
    websites/staging/trafficserver/trunk/cgi-bin/   (props changed)
    websites/staging/trafficserver/trunk/content/   (props changed)
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html

Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb  6 07:18:11 2013
@@ -1 +1 @@
-1442194
+1442855

Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Feb  6 07:18:11 2013
@@ -1 +1 @@
-1442194
+1442855

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html Wed Feb  6 07:18:11 2013
@@ -119,6 +119,7 @@ the <code>records.config</code> file.</p
 <dt id="proxy.config.proxy_name"><em><code>proxy.config.proxy_name</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd>Default: <em><code>build_machine</code></em></dd>
+<dd>Reloadable.</dd>
 <dd>The name of the Traffic Server node.</dd>
 <dt id="proxy.config.bin_path"><em><code>proxy.config.bin_path</code></em></dt>
 <dd><code>STRING</code></dd>
@@ -159,6 +160,7 @@ the <code>records.config</code> file.</p
 <dt id="proxy.config.alarm_email"><em><code>proxy.config.alarm_email</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd>Default: (none)</dd>
+<dd>Reloadable.</dd>
 <dd>The email address to which Traffic Server sends alarm messages. During a custom Traffic Server installation, you can specify the email address; otherwise, Traffic Server uses the Traffic Server user account name as the default value for this variable.</dd>
 <dt id="proxy.config.syslog_facility"><em><code>proxy.config.syslog_facility</code></em></dt>
 <dd><code>STRING</code></dd>
@@ -419,6 +421,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>You can specify one of the following:</p>
 <ul>
 <li><code>0</code> = no extra information is added to the string.</li>
@@ -435,6 +440,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>You can specify one of the following:</p>
 <ul>
 <li><code>0</code> no extra information is added to the string.</li>
@@ -450,6 +458,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>You can specify one of the following:</p>
 <ul>
 <li><code>0</code> no Server: header is added to the response.</li>
@@ -465,6 +476,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>This option specifies whether Traffic Server should insert an <code>Age</code> header in the response. The Age field value is the cache's estimate of the amount of time since the response was generated or revalidated by the origin server.</p>
 <ul>
 <li><code>0</code> no <code>Age</code> header is added</li>
@@ -479,6 +493,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>ATS/</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The Server: string that ATS will insert in a response header (if requested, see above). Note that the current version number is always appended to this string.</p>
 </dd>
 <dt id="proxy.config.http.enable_url_expandomatic"><em><code>proxy.config.http.enable_url_expandomatic</code></em></dt>
@@ -489,6 +506,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) <code>.com</code> domain expansion. This configures the Traffic Server to resolve unqualified hostnames by prepending with <code>www.</code> and appending with <code>.com</code> before redirecting to the expanded address.  For example: if a client makes a request to <code>host</code>, then Traffic Server redirects the request to <code>www.host.com</code>.</p>
 </dd>
 <dt id="proxy.config.http.chunking_enabled"><em><code>proxy.config.http.chunking_enabled</code></em></dt>
@@ -499,6 +519,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Specifies whether Traffic Sever can generate a chunked response:</p>
 <ul>
 <li><code>0</code> Never</li>
@@ -526,6 +549,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) <code>traffic_cop</code> heartbeat logging.</p>
 </dd>
 <dt id="proxy.config.http.use_client_target_addr"><em><code>proxy.config.http.use_client_target_addr</code></em></dt>
@@ -536,6 +562,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Avoid DNS lookup for forward transparent requests:</p>
 <ul>
 <li><code>0</code> Never.</li>
@@ -567,30 +596,37 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.parent_proxy_routing_enable"><em><code>proxy.config.http.parent_proxy_routing_enable</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) the parent caching option. Refer to <a href="../hierachical-caching">Hierarchical Caching</a>.</dd>
 <dt id="proxy.config.http.parent_proxy.retry_time"><em><code>proxy.config.http.parent_proxy.retry_time</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>300</code></dd>
+<dd>Reloadable.</dd>
 <dd>The amount of time allowed between connection retries to a parent cache that is unavailable.</dd>
 <dt id="proxy.config.http.parent_proxy.fail_threshold"><em><code>proxy.config.http.parent_proxy.fail_threshold</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>10</code></dd>
+<dd>Reloadable.</dd>
 <dd>The number of times the connection to the parent cache can fail before Traffic Server considers the parent unavailable.</dd>
 <dt id="proxy.config.http.parent_proxy.total_connect_attempts"><em><code>proxy.config.http.parent_proxy.total_connect_attempts</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>4</code></dd>
+<dd>Reloadable.</dd>
 <dd>The total number of connection attempts allowed to a parent cache before Traffic Server bypasses the parent or fails the request (depending on the <em><code>go_direct</code></em> option in the <code>bypass.config</code> file).</dd>
 <dt id="proxy.config.http.parent_proxy.per_parent_connect_attempts"><em><code>proxy.config.http.parent_proxy.per_parent_connect_attempts</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>2</code></dd>
+<dd>Reloadable.</dd>
 <dd>The total number of connection attempts allowed per parent, if multiple parents are used.</dd>
 <dt id="proxy.config.http.parent_proxy.connect_attempts_timeout"><em><code>proxy.config.http.parent_proxy.connect_attempts_timeout</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>30</code></dd>
+<dd>Reloadable.</dd>
 <dd>The timeout value (in seconds) for parent cache connection attempts.</dd>
 <dt id="proxy.config.http.forward.proxy_auth_to_parent"><em><code>proxy.config.http.forward.proxy_auth_to_parent</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Configures Traffic Server to send proxy authentication headers on to the parent cache.</dd>
 </dl>
 <h1 id="HTTPConnectionTimeouts">HTTP Connection Timeouts</h1>
@@ -598,40 +634,49 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.keep_alive_no_activity_timeout_in"><em><code>proxy.config.http.keep_alive_no_activity_timeout_in</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>10</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies how long Traffic Server keeps connections to clients open for a subsequent request after a transaction ends.</dd>
 <dt id="proxy.config.http.keep_alive_no_activity_timeout_out"><em><code>proxy.config.http.keep_alive_no_activity_timeout_out</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>10</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies how long Traffic Server keeps connections to origin servers open for a subsequent transfer of data after a transaction ends.</dd>
 <dt id="proxy.config.http.transaction_no_activity_timeout_in"><em><code>proxy.config.http.transaction_no_activity_timeout_in</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>120</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies how long Traffic Server keeps connections to clients open if a transaction stalls.</dd>
 <dt id="proxy.config.http.transaction_no_activity_timeout_out"><em><code>proxy.config.http.transaction_no_activity_timeout_out</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>120</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies how long Traffic Server keeps connections to origin servers open if the transaction stalls.</dd>
 <dt id="proxy.config.http.transaction_active_timeout_in"><em><code>proxy.config.http.transaction_active_timeout_in</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>The maximum amount of time Traffic Server can remain connected to a client. If the transfer to the client is not complete before this timeout expires, then Traffic Server closes the connection.
  The default value of <code>0</code> specifies that there is no timeout.</dd>
 <dt id="proxy.config.http.transaction_active_timeout_out"><em><code>proxy.config.http.transaction_active_timeout_out</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>The maximum amount of time Traffic Server waits for fulfillment of a connection request to an origin server. If Traffic Server does not complete the transfer to the origin server before this timeout expires, then Traffic Server terminates the connection request.
  The default value of <code>0</code> specifies that there is no timeout.</dd>
 <dt id="proxy.config.http.accept_no_activity_timeout"><em><code>proxy.config.http.accept_no_activity_timeout</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>120</code></dd>
+<dd>Reloadable.</dd>
 <dd>The timeout interval in seconds before Traffic Server closes a connection that has no activity.</dd>
 <dt id="proxy.config.http.background_fill_active_timeout"><em><code>proxy.config.http.background_fill_active_timeout</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>60</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies how long Traffic Server continues a background fill before giving up and dropping the origin server connection.</dd>
 <dt id="proxy.config.http.background_fill_completed_threshold"><em><code>proxy.config.http.background_fill_completed_threshold</code></em></dt>
 <dd><code>FLOAT</code></dd>
 <dd>Default: <code>0.50000</code></dd>
+<dd>Reloadable.</dd>
 <dd>The proportion of total document size already transferred when a client aborts at which the proxy continues fetching the document from the origin server to get it into the cache (a <strong>background fill</strong>).</dd>
 </dl>
 <h1 id="OriginServerConnectAttempts">Origin Server Connect Attempts</h1>
@@ -639,42 +684,52 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.connect_attempts_max_retries"><em><code>proxy.config.http.connect_attempts_max_retries</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>6</code></dd>
+<dd>Reloadable.</dd>
 <dd>The maximum number of connection retries Traffic Server can make when the origin server is not responding.</dd>
 <dt id="proxy.config.http.connect_attempts_max_retries_dead_server"><em><code>proxy.config.http.connect_attempts_max_retries_dead_server</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>2</code></dd>
+<dd>Reloadable.</dd>
 <dd>The maximum number of connection retries Traffic Server can make when the origin server is unavailable.</dd>
 <dt id="proxy.config.http.server_max_connections"><em><code>proxy.config.http.server_max_connections</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Limits the number of socket connections across all origin servers to the value specified. To disable, set to zero (<code>0</code>).</dd>
 <dt id="proxy.config.http.origin_max_connections"><em><code>proxy.config.http.origin_max_connections</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Limits the number of socket connections per origin server to the value specified. To enable, set to one (<code>1</code>).</dd>
 <dt id="proxy.config.http.origin_min_keep_alive_connections"><em><code>proxy.config.http.origin_min_keep_alive_connections</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>As connection to an origin server are opened, keep at least 'n' number of connections open to that origin, even if the connection isn't used for a long time period. Useful when the origin supports keep-alive, removing the time needed to set up a new connection from the next request at the expense of added (inactive) connections. To enable, set to one (<code>1</code>).</dd>
 <dt id="proxy.config.http.connect_attempts_rr_retries"><em><code>proxy.config.http.connect_attempts_rr_retries</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>2</code></dd>
+<dd>Reloadable.</dd>
 <dd>The maximum number of failed connection attempts allowed before a round-robin entry is marked as 'down' if a server has round-robin DNS entries.</dd>
 <dt id="proxy.config.http.connect_attempts_timeout"><em><code>proxy.config.http.connect_attempts_timeout</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>30</code></dd>
+<dd>Reloadable.</dd>
 <dd>The timeout value (in seconds) for an origin server connection.</dd>
 <dt id="proxy.config.http.post_connect_attempts_timeout"><em><code>proxy.config.http.post_connect_attempts_timeout</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>1800</code></dd>
+<dd>Reloadable.</dd>
 <dd>The timeout value (in seconds) for an origin server connection when the client request is a <code>POST</code> or <code>PUT</code> request.</dd>
 <dt id="proxy.config.http.down_server.cache_time"><em><code>proxy.config.http.down_server.cache_time</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>900</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies how long (in seconds) Traffic Server remembers that an origin server was unreachable.</dd>
 <dt id="proxy.config.http.down_server.abort_threshold"><em><code>proxy.config.http.down_server.abort_threshold</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>10</code></dd>
+<dd>Reloadable.</dd>
 <dd>The number of seconds before Traffic Server marks an origin server as unavailable after a client abandons a request because the origin server was too slow in sending the response header.</dd>
 </dl>
 <h1 id="CongestionControl">Congestion Control</h1>
@@ -689,6 +744,7 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.negative_caching_enabled"><em><code>proxy.config.http.negative_caching_enabled</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>
 <p>When enabled (<code>1</code>), Traffic Server caches negative responses (such as <code>404 Not Found</code>) when a requested page does not exist. The next time a client requests the same page, Traffic Server serves the negative response directly from cache.</p>
 <p><strong>Note</strong>: <code>Cache-Control</code> directives from the server forbidding cache are ignored for the following HTTP response codes, regardless of the value specified for the <em><code>proxy.config.http.negative_caching_enabled</code></em> variable. The following negative responses are cached by Traffic Server:</p>
@@ -713,26 +769,32 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.anonymize_remove_from"><em><code>proxy.config.http.anonymize_remove_from</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server removes the <code>From</code> header to protect the privacy of your users.</dd>
 <dt id="proxy.config.http.anonymize_remove_referer"><em><code>proxy.config.http.anonymize_remove_referer</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server removes the <code>Referrer</code> header to protect the privacy of your site and users.</dd>
 <dt id="proxy.config.http.anonymize_remove_user_agent"><em><code>proxy.config.http.anonymize_remove_user_agent</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server removes the <code>User-agent</code> header to protect the privacy of your site and users.</dd>
 <dt id="proxy.config.http.anonymize_remove_cookie"><em><code>proxy.config.http.anonymize_remove_cookie</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server removes the <code>Cookie</code> header to protect the privacy of your site and users.</dd>
 <dt id="proxy.config.http.anonymize_remove_client_ip"><em><code>proxy.config.http.anonymize_remove_client_ip</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server removes <code>Client-IP</code> headers for more privacy.</dd>
 <dt id="proxy.config.http.anonymize_insert_client_ip"><em><code>proxy.config.http.anonymize_insert_client_ip</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>1</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server inserts <code>Client-IP</code> headers to retain the client IP address.</dd>
 <dt id="proxy.config.http.append_xforwards_header"><em><code>proxy.config.http.append_xforwards_header</code></em></dt>
 <dd><code>INT</code></dd>
@@ -741,14 +803,17 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.anonymize_other_header_list"><em><code>proxy.config.http.anonymize_other_header_list</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd>Default: <code>NULL</code></dd>
+<dd>Reloadable.</dd>
 <dd>The headers Traffic Server should remove from outgoing requests.</dd>
 <dt id="proxy.config.http.insert_squid_x_forwarded_for"><em><code>proxy.config.http.insert_squid_x_forwarded_for</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server adds the client IP address to the <code>X-Forwarded-For</code> header.</dd>
 <dt id="proxy.config.http.normalize_ae_gzip"><em><code>proxy.config.http.normalize_ae_gzip</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>
 <p>Enable (<code>1</code>) to normalize all <code>Accept-Encoding:</code> headers to one of the following:</p>
 <ul>
@@ -763,6 +828,7 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.push_method_enabled"><em><code>proxy.config.http.push_method_enabled</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) the HTTP <code>PUSH</code> option, which allows you to deliver content directly to the cache without a user request.</p>
 <p><strong>Important:</strong> If you enable this option, then you must also specify a filtering rule in the <a href="ip_allow.config"><code>ip_allow.config</code></a> file to allow only certain machines to push content into the cache.</p>
@@ -773,30 +839,37 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.cache.enable_read_while_writer"><em><code>proxy.config.cache.enable_read_while_writer</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) ability to a read cached object while the another connection is completing the write to cache for the same object. This must be enabled for connection collapsing to work</dd>
 <dt id="proxy.config.cache.force_sector_size"><em><code>proxy.config.cache.force_sector_size</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>512</code></dd>
+<dd>Reloadable.</dd>
 <dd>Forces the use of a specific hardware sector size (512 - 8192 bytes).</dd>
 <dt id="proxy.config.http.cache.http"><em><code>proxy.config.http.cache.http</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>1</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) caching of HTTP requests.</dd>
 <dt id="proxy.config.http.cache.ignore_client_no_cache"><em><code>proxy.config.http.cache.ignore_client_no_cache</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server ignores client requests to bypass the cache.</dd>
 <dt id="proxy.config.http.cache.ims_on_client_no_cache"><em><code>proxy.config.http.cache.ims_on_client_no_cache</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server issues a conditional request to the origin server if an incoming request has a <code>No-Cache</code> header.</dd>
 <dt id="proxy.config.http.cache.ignore_server_no_cache"><em><code>proxy.config.http.cache.ignore_server_no_cache</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>When enabled (<code>1</code>), Traffic Server ignores origin server requests to bypass the cache.</dd>
 <dt id="proxy.config.http.cache.cache_responses_to_cookies"><em><code>proxy.config.http.cache.cache_responses_to_cookies</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>3</code></dd>
+<dd>Reloadable.</dd>
 <dd>
 <p>Specifies how cookies are cached:</p>
 <ul>
@@ -824,6 +897,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) caching of URLs that look dynamic, i.e.: URLs that end in <strong><code>.asp</code></strong> or contain a question mark (<strong><code>?</code></strong>), a semicolon (<strong><code>;</code></strong>), or <strong><code>cgi</code></strong>. For a full list, please refer to <a href="/link/to/doxygen">HttpTransact::url_looks_dynamic</a></p>
 </dd>
 <dt id="proxy.config.http.cache.enable_default_vary_headers"><em><code>proxy.config.http.cache.enable_default_vary_headers</code></em></dt>
@@ -834,6 +910,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) caching of alternate versions of HTTP objects that do not contain the <code>Vary</code> header.</p>
 </dd>
 <dt id="proxy.config.http.cache.when_to_revalidate"><em><code>proxy.config.http.cache.when_to_revalidate</code></em></dt>
@@ -844,6 +923,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Specifies when to revalidate content:</p>
 <ul>
 <li><code>0</code> = use cache directives or heuristic (the default value)</li>
@@ -863,6 +945,9 @@ would listen to ports <code>6060</code>,
 <p>Default: 0</p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Specifies when to add <code>no-cache</code> directives to Microsoft Internet Explorer requests. You can specify the following:</p>
 <ul>
 <li><code>0</code> = <code>no-cache</code> is <em>not</em> added to MSIE requests</li>
@@ -878,6 +963,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The type of headers required in a request for the request to be cacheable.</p>
 <ul>
 <li><code>0</code> = no headers required to make document cacheable</li>
@@ -893,6 +981,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>604800</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The maximum age allowed for a stale response before it cannot be cached.</p>
 </dd>
 <dt id="proxy.config.http.cache.range.lookup"><em><code>proxy.config.http.cache.range.lookup</code></em></dt>
@@ -953,6 +1044,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Sets a minimum fuzz time; the default value is <code>0</code>.  <strong>Effective fuzz time</strong> is a calculation in the range (<code>fuzz.min_time</code> - <code>fuzz.min_time</code>).</p>
 </dd>
 <dt id="proxy.config.http.cache.ignore_accept_mismatch"><em><code>proxy.config.http.cache.ignore_accept_mismatch</code></em></dt>
@@ -963,6 +1057,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), Traffic Server serves documents from cache with a <code>Content-Type:</code> header that does not match the <code>Accept:</code> header of the request.</p>
 <p><strong>Note:</strong> This option should only be enabled if you're having problems with caching <em>and</em> one of the following is true:</p>
 <ul>
@@ -978,6 +1075,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), Traffic Server serves documents from cache with a <code>Content-Language:</code> header that does not match the <code>Accept-Language:</code> header of the request.</p>
 <p><strong>Note:</strong> This option should only be enabled if you're having problems with caching and your origin server is guaranteed to set <code>Vary: Accept-Language</code> when doing content negotiation with <code>Accept-Language</code>.</p>
 </dd>
@@ -989,6 +1089,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), Traffic Server serves documents from cache with a <code>Content-Type:</code> header that does not match the <code>Accept-Charset:</code> header of the request.</p>
 <p><strong>Note:</strong> This option should only be enabled if you're having problems with caching and your origin server is guaranteed to set <code>Vary: Accept-Charset</code> when doing content negotiation with <code>Accept-Charset</code>.</p>
 </dd>
@@ -1000,6 +1103,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), Traffic Server ignores any <code>Cache-Control:  max-age</code> headers from the client.</p>
 </dd>
 <dt id="proxy.config.cache.permit.pinning"><em><code>proxy.config.cache.permit.pinning</code></em></dt>
@@ -1010,6 +1116,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), Traffic Server will keep certain HTTP objects in the cache for a certain time as  specified in <a href="cache.config"><code>cache.config</code></a>.</p>
 </dd>
 </dl>
@@ -1018,22 +1127,27 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.cache.heuristic_min_lifetime"><em><code>proxy.config.http.cache.heuristic_min_lifetime</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>3600</code> (1 hour)</dd>
+<dd>Reloadable.</dd>
 <dd>The minimum amount of time an HTTP object without an expiration date can remain fresh in the cache before is considered to be stale.</dd>
 <dt id="proxy.config.http.cache.heuristic_max_lifetime"><em><code>proxy.config.http.cache.heuristic_max_lifetime</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>86400</code> (1 day)</dd>
+<dd>Reloadable.</dd>
 <dd>The maximum amount of time an HTTP object without an expiration date can remain fresh in the cache before is considered to be stale.</dd>
 <dt id="proxy.config.http.cache.heuristic_lm_factor"><em><code>proxy.config.http.cache.heuristic_lm_factor</code></em></dt>
 <dd><code>FLOAT</code></dd>
 <dd>Default: <code>0.10000</code></dd>
+<dd>Reloadable.</dd>
 <dd>The aging factor for freshness computations. Traffic Server stores an object for this percentage of the time that elapsed since it last changed.</dd>
 <dt id="proxy.config.http.cache.fuzz.time"><em><code>proxy.config.http.cache.fuzz.time</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>240</code></dd>
+<dd>Reloadable.</dd>
 <dd>How often Traffic Server checks for an early refresh, during the period before the document stale time. The interval specified must be in seconds.</dd>
 <dt id="proxy.config.http.cache.fuzz.probability"><em><code>proxy.config.http.cache.fuzz.probability</code></em></dt>
 <dd><code>FLOAT</code></dd>
 <dd>Default: <code>0.00500</code></dd>
+<dd>Reloadable.</dd>
 <dd>The probability that a refresh is made on a document during the specified fuzz time.</dd>
 </dl>
 <h1 id="DynamicContentAndContentNegotiation">Dynamic Content &amp; Content Negotiation</h1>
@@ -1041,15 +1155,18 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.http.cache.vary_default_text"><em><code>proxy.config.http.cache.vary_default_text</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd>Default: <code>NULL</code></dd>
+<dd>Reloadable.</dd>
 <dd>The header on which Traffic Server varies for text documents.
  For example: if you specify <code>User-agent</code>, then Traffic Server caches all the different user-agent versions of documents it encounters.</dd>
 <dt id="proxy.config.http.cache.vary_default_images"><em><code>proxy.config.http.cache.vary_default_images</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd>Default: <code>NULL</code></dd>
+<dd>Reloadable.</dd>
 <dd>The header on which Traffic Server varies for images.</dd>
 <dt id="proxy.config.http.cache.vary_default_other"><em><code>proxy.config.http.cache.vary_default_other</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd>Default: <code>NULL</code></dd>
+<dd>Reloadable.</dd>
 <dd>The header on which Traffic Server varies for anything other than text and images.</dd>
 </dl>
 <h1 id="CustomizableUserResponsePages">Customizable User Response Pages</h1>
@@ -1106,10 +1223,12 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.dns.search_default_domains"><em><code>proxy.config.dns.search_default_domains</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>1</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) local domain expansion so that Traffic Server can attempt to resolve unqualified hostnames by expanding to the local domain. For example: if a client makes a request to an unqualified host (<code>host_x</code>) and the Traffic Server local domain is <code>y.com</code> , then Traffic Server will expand the hostname to <code>host_x.y.com</code>.</dd>
 <dt id="proxy.config.dns.splitDNS.enabled"><em><code>proxy.config.dns.splitDNS.enabled</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) DNS server selection.   When enabled, Traffic Server refers to the <code>splitdns.config</code> file for the selection specification. Refer to <a href="../security-options#ConfiguringDNSServerSelectionSplit">Configuring DNS Server Selection (Split DNS)</a>.</dd>
 <dt id="proxy.config.dns.url_expansions"><em><code>proxy.config.dns.url_expansions</code></em></dt>
 <dd><code>STRING</code></dd>
@@ -1136,6 +1255,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) DNS server round-robin.</p>
 </dd>
 <dt id="proxy.config.dns.nameservers"><em><code>proxy.config.dns.nameservers</code></em></dt>
@@ -1146,6 +1268,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>NULL</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The DNS servers.</p>
 </dd>
 <dt id="proxy.config.srv_enabled"><em><code>proxy.config.srv_enabled</code></em></dt>
@@ -1156,6 +1281,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Indicates whether to use SRV records for orgin server lookup.</p>
 </dd>
 </dl>
@@ -1179,6 +1307,7 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.hostdb.ttl_mode"><em><code>proxy.config.hostdb.ttl_mode</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>
 <p>The host database time to live mode. You can specify one of the following:</p>
 <ul>
@@ -1196,6 +1325,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1440</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The foreground timeout (in minutes).</p>
 </dd>
 <dt id="proxy.config.hostdb.strict_round_robin"><em><code>proxy.config.hostdb.strict_round_robin</code></em></dt>
@@ -1206,6 +1338,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When disabled (<code>0</code>), Traffic Server always uses the same origin server for the same client, for as long as the origin server is available.</p>
 </dd>
 </dl>
@@ -1214,6 +1349,7 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.log.logging_enabled"><em><code>proxy.config.log.logging_enabled</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>3</code></dd>
+<dd>Reloadable.</dd>
 <dd>
 <p>Enables and disables event logging:</p>
 <ul>
@@ -1232,6 +1368,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>5</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The maximum amount of time before data in the buffer is flushed to disk.</p>
 </dd>
 <dt id="proxy.config.log.max_space_mb_for_logs"><em><code>proxy.config.log.max_space_mb_for_logs</code></em></dt>
@@ -1242,6 +1381,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>2000</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The amount of space allocated to the logging directory (in MB).  <strong>Note:</strong> All files in the logging directory contribute to the space used, even if they are not log files. In collation client mode, if there is no local disk logging, or max_space_mb_for_orphan_logs is set to a higher value than max_space_mb_for_logs, TS will take proxy.config.log.max_space_mb_for_orphan_logs for maximum allowed log space.</p>
 </dd>
 <dt id="proxy.config.log.max_space_mb_for_orphan_logs"><em><code>proxy.config.log.max_space_mb_for_orphan_logs</code></em></dt>
@@ -1252,6 +1394,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>25</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The amount of space allocated to the logging directory (in MB) if this node is acting as a collation client. <strong>Note:</strong> When max_space_mb_for_orphan_logs is take as the maximum allowedlog space in the logging system, the same rule apply to proxy.config.log.max_space_mb_for_logs also apply to proxy.config.log.max_space_mb_for_orphan_logs, ie: All files in the logging directory contribute to the space used, even if they are not log files. you may need to consider this when you enable full remote logging, and bump to the same size as proxy.config.log.max_space_mb_for_logs.</p>
 </dd>
 <dt id="proxy.config.log.max_space_mb_headroom"><em><code>proxy.config.log.max_space_mb_headroom</code></em></dt>
@@ -1262,6 +1407,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>10</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The tolerance for the log space limit (in bytes). If the variable <em><code>proxy.config.log.auto_delete_rolled_file</code></em> is set to <code>1</code> (enabled), then autodeletion of log files is triggered when the amount of free space available in the logging directory is less than the value specified here.</p>
 </dd>
 <dt id="proxy.config.log.hostname"><em><code>proxy.config.log.hostname</code></em></dt>
@@ -1272,6 +1420,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>localhost</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The hostname of the machine running Traffic Server.</p>
 </dd>
 <dt id="proxy.config.log.logfile_dir"><em><code>proxy.config.log.logfile_dir</code></em></dt>
@@ -1282,6 +1433,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <em><code>install_dir</code></em><code>/logs</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The full path to the logging directory. This can be an absolute path or a path relative to the directory in which Traffic Server is installed. <strong>Note:</strong> The directory you specify must already exist.</p>
 </dd>
 <dt id="proxy.config.log.logfile_perm"><em><code>proxy.config.log.logfile_perm</code></em></dt>
@@ -1292,6 +1446,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>rw-r--r--</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The log file permissions. The standard UNIX file permissions are used (owner, group, other). Permissible values are:</p>
 <p><code>-</code>no permission
 <code>r</code>read permission
@@ -1307,6 +1464,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) custom logging.</p>
 </dd>
 <dt id="proxy.config.log.squid_log_enabled"><em><code>proxy.config.log.squid_log_enabled</code></em></dt>
@@ -1317,6 +1477,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) the <a href="../working-log-files/log-formats#SquidFormat">squid log file format</a>.</p>
 </dd>
 <dt id="proxy.config.log.squid_log_is_ascii"><em><code>proxy.config.log.squid_log_is_ascii</code></em></dt>
@@ -1327,6 +1490,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The squid log file type:</p>
 <ul>
 <li><code>1</code> = ASCII</li>
@@ -1341,6 +1507,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>squid</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#SquidFormat">squid log</a> filename.</p>
 </dd>
 <dt id="proxy.config.log.squid_log_header"><em><code>proxy.config.log.squid_log_header</code></em></dt>
@@ -1361,6 +1530,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) the <a href="../working-log-files/log-formats#NetscapeFormats">Netscape common log file format</a>.</p>
 </dd>
 <dt id="proxy.config.log.common_log_is_ascii"><em><code>proxy.config.log.common_log_is_ascii</code></em></dt>
@@ -1371,6 +1543,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#NetscapeFormats">Netscape common log</a> file type:</p>
 <ul>
 <li><code>1</code> = ASCII</li>
@@ -1385,6 +1560,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>common</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#NetscapeFormats">Netscape common log</a> filename.</p>
 </dd>
 <dt id="proxy.config.log.common_log_header"><em><code>proxy.config.log.common_log_header</code></em></dt>
@@ -1395,6 +1573,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>NULL</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#NetscapeFormats">Netscape common log</a> file header text.</p>
 </dd>
 <dt id="proxy.config.log.extended_log_enabled"><em><code>proxy.config.log.extended_log_enabled</code></em></dt>
@@ -1405,6 +1586,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) the <a href="../working-log-files/log-formats#NetscapeFormats">Netscape extended log file format</a>.</p>
 </dd>
 <dt id="proxy.confg.log.extended_log_is_ascii"><em><code>proxy.confg.log.extended_log_is_ascii</code></em></dt>
@@ -1439,6 +1623,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>NULL</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#NetscapeFormats">Netscape extended log</a> file header text.</p>
 </dd>
 <dt id="proxy.config.log.extended2_log_enabled"><em><code>proxy.config.log.extended2_log_enabled</code></em></dt>
@@ -1449,6 +1636,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) the <a href="../working-log-files/log-formats#NetscapeFormats">Netscape Extended-2 log file format</a>.</p>
 </dd>
 <dt id="proxy.config.log.extended2_log_is_ascii"><em><code>proxy.config.log.extended2_log_is_ascii</code></em></dt>
@@ -1459,6 +1649,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#NetscapeFormats">Netscape Extended-2 log</a> file type:</p>
 <ul>
 <li><code>1</code> = ASCII</li>
@@ -1473,6 +1666,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>extended2</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#NetscapeFormats">Netscape Extended-2 log</a> filename.</p>
 </dd>
 <dt id="proxy.config.log.extended2_log_header"><em><code>proxy.config.log.extended2_log_header</code></em></dt>
@@ -1483,6 +1679,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>NULL</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The <a href="../working-log-files/log-formats#NetscapeFormats">Netscape Extended-2 log</a> file header text.</p>
 </dd>
 <dt id="proxy.config.log.separate_icp_logs"><em><code>proxy.config.log.separate_icp_logs</code></em></dt>
@@ -1493,6 +1692,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), configures Traffic Server to store ICP transactions in a separate log file.</p>
 <ul>
 <li><code>0</code> = separation is disabled, all ICP transactions are recorded in the same file as HTTP transactions</li>
@@ -1508,6 +1710,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), configures Traffic Server to create a separate log file for HTTP transactions for each origin server listed in the <code>log_hosts.config</code> file. Refer to <a href="../working-log-files#HTTPHostLogSplitting">HTTP Host Log Splitting</a>.</p>
 </dd>
 <dt id="proxy.local.log.collation_mode"><em><code>proxy.local.log.collation_mode</code></em></dt>
@@ -1518,6 +1723,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The log collation mode:</p>
 <ul>
 <li><code>0</code> = collation is disabled</li>
@@ -1547,6 +1755,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>8085</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The port used for communication between the collation server and client.</p>
 </dd>
 <dt id="proxy.config.log.collation_secret"><em><code>proxy.config.log.collation_secret</code></em></dt>
@@ -1557,6 +1768,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>foobar</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The password used to validate logging data and prevent the exchange of unauthorized information when a collation server is being used.</p>
 </dd>
 <dt id="proxy.config.log.collation_host_tagged"><em><code>proxy.config.log.collation_host_tagged</code></em></dt>
@@ -1567,6 +1781,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>When enabled (<code>1</code>), configures Traffic Server to include the hostname of the collation client that generated the log entry in each entry.</p>
 </dd>
 <dt id="proxy.config.log.collation_retry_sec"><em><code>proxy.config.log.collation_retry_sec</code></em></dt>
@@ -1577,6 +1794,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>5</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The number of seconds between collation server connection retries.</p>
 </dd>
 <dt id="proxy.config.log.rolling_enabled"><em><code>proxy.config.log.rolling_enabled</code></em></dt>
@@ -1587,6 +1807,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Specifies how log files are rolled. You can specify the following values:</p>
 <ul>
 <li><code>0</code> = disables log file rolling</li>
@@ -1604,6 +1827,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>86400</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The log file rolling interval, in seconds. The minimum value is <code>300</code> (5 minutes). The maximum value is 86400 seconds (one day).</p>
 <p><strong>Note:</strong> If you start Traffic Server within a few minutes of the next rolling time,  then rolling might not occur until the next rolling time.</p>
 </dd>
@@ -1615,6 +1841,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The file rolling offset hour. The hour of the day that starts the log rolling period.</p>
 </dd>
 <dt id="proxy.config.log.rolling_size_mb"><em><code>proxy.config.log.rolling_size_mb</code></em></dt>
@@ -1625,6 +1854,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>10</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The size that log files must reach before rolling takes place.</p>
 </dd>
 <dt id="proxy.config.log.auto_delete_rolled_files"><em><code>proxy.config.log.auto_delete_rolled_files</code></em></dt>
@@ -1635,6 +1867,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Enables (<code>1</code>) or disables (<code>0</code>) automatic deletion of rolled files.</p>
 </dd>
 <dt id="proxy.config.log.sampling_frequency"><em><code>proxy.config.log.sampling_frequency</code></em></dt>
@@ -1645,6 +1880,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>1</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Configures Traffic Server to log only a sample of transactions rather than every transaction. You can specify the following values:</p>
 <ul>
 <li><code>1</code> = log every transaction</li>
@@ -1660,6 +1898,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>0</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>The number of milliseconds before a slow connection's debugging stats are dumped. Specify <code>1</code> to enable or <code>0</code> to disable.</p>
 </dd>
 </dl>
@@ -1695,10 +1936,12 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.reverse_proxy.enabled"><em><code>proxy.config.reverse_proxy.enabled</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>1</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) HTTP reverse proxy.</dd>
 <dt id="proxy.config.header.parse.no_host_url_redirect"><em><code>proxy.config.header.parse.no_host_url_redirect</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd>Default: <code>NULL</code></dd>
+<dd>Reloadable.</dd>
 <dd>The URL to which to redirect requests with no host headers (reverse proxy).</dd>
 </dl>
 <h1 id="URLRemapRules">URL Remap Rules</h1>
@@ -1706,18 +1949,22 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.url_remap.default_to_server_pac"><em><code>proxy.config.url_remap.default_to_server_pac</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) requests for a PAC file on the proxy service port (8080 by default) to be redirected to the PAC port. For this type of redirection to work, the variable <em><code>proxy.config.reverse_proxy.enabled</code></em> must be set to <code>1</code>.</dd>
 <dt id="proxy.config.url_remap.default_to_server_pac_port"><em><code>proxy.config.url_remap.default_to_server_pac_port</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>-1</code></dd>
+<dd>Reloadable.</dd>
 <dd>Sets the PAC port so that PAC requests made to the Traffic Server proxy service port are redirected this port. <code>-1</code> is the default setting that sets the PAC port to the autoconfiguration port (the default autoconfiguration port is 8083).  This variable can be used together with the <em><code>proxy.config.url_remap.default_to_server_pac</code></em> variable to get a PAC file from a different port. You must create and run a process that serves a PAC file on this port.  For example: if you create a Perl script that listens on port 9000 and writes a PAC file in response to any request, then you can set this variable to <code>9000</code>. Browsers that request the PAC file from a proxy server on port 8080 will get the PAC file served by the Perl script.</dd>
 <dt id="proxy.config.url_remap.remap_required"><em><code>proxy.config.url_remap.remap_required</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>1</code></dd>
+<dd>Reloadable.</dd>
 <dd>Set this variable to <code>1</code> if you want Traffic Server to serve requests only from origin servers listed in the mapping rules of the <code>remap.config</code> file. If a request does not match, then the browser will receive an error.</dd>
 <dt id="proxy.config.url_remap.pristine_host_hdr"><em><code>proxy.config.url_remap.pristine_host_hdr</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>1</code></dd>
+<dd>Reloadable.</dd>
 <dd>Set this variable to <code>1</code> if you want to retain the client host header in a request during remapping.</dd>
 </dl>
 <h1 id="SSLTermination">SSL Termination</h1>
@@ -1955,6 +2202,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>3130</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Specifies the UDP port that you want to use for ICP messages.</p>
 </dd>
 <dt id="proxy.config.icp.query_timeout"><em><code>proxy.config.icp.query_timeout</code></em></dt>
@@ -1965,6 +2215,9 @@ would listen to ports <code>6060</code>,
 <p>Default: <code>2</code></p>
 </dd>
 <dd>
+<p>Reloadable.</p>
+</dd>
+<dd>
 <p>Specifies the timeout used for ICP queries.</p>
 </dd>
 </dl>
@@ -1977,18 +2230,22 @@ would listen to ports <code>6060</code>,
 <dt id="proxy.config.update.force"><em><code>proxy.config.update.force</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>0</code></dd>
+<dd>Reloadable.</dd>
 <dd>Enables (<code>1</code>) or disables (<code>0</code>) a force immediate update. When enabled, Traffic Server overrides the scheduling expiration time for all scheduled update entries and initiates updates until this option is disabled.</dd>
 <dt id="proxy.config.update.retry_count"><em><code>proxy.config.update.retry_count</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>10</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies the number of times Traffic Server can retry the scheduled update of a URL in the event of failure.</dd>
 <dt id="proxy.config.update.retry_interval"><em><code>proxy.config.update.retry_interval</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>2</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies the delay (in seconds) between each scheduled update retry for a URL in the event of failure.</dd>
 <dt id="proxy.config.update.concurrent_updates"><em><code>proxy.config.update.concurrent_updates</code></em></dt>
 <dd><code>INT</code></dd>
 <dd>Default: <code>100</code></dd>
+<dd>Reloadable.</dd>
 <dd>Specifies the maximum simultaneous update requests allowed at any time. This option prevents the scheduled update process from overburdening the host.</dd>
 </dl>
 <h1 id="RemapPluginProcessor">Remap Plugin Processor</h1>



Mime
View raw message