Today we had an issue with an origin which threw some 500 errors. We
noticed that trafficserver cached the responses even though we had negative
caching disabled. When we went to dig into this we noticed that the docs
are a bit confusing (missing newline after NOTE and response code list) and
somewhat incomplete-- if a response has cache control directives it will be
cached regardless of response code.
This is my first commit to the docs, so hopefully I've done it correctly if
not please let me know!
Thomas Jackson
Index: content/docs/trunk/admin/configuration-files/records.config.en.mdtext
===================================================================
--- content/docs/trunk/admin/configuration-files/records.config.en.mdtext (revision 1535893)
+++ content/docs/trunk/admin/configuration-files/records.config.en.mdtext (working copy)
@@ -387,8 +387,8 @@
: You can specify one of the following:
* `0` no extra information is added to the string.
- * `1` all extra information is added.
- * `2` some extra information is added.
+ * `1` all extra information is added.
+ * `2` some extra information is added.
*`proxy.config.http.response_server_enabled`* {#proxy.config.http.response_server_enabled}
: `INT`
@@ -429,7 +429,7 @@
* `0` Never
* `1` Always
- * `2` Generate a chunked response if the server has returned HTTP/1.1 before
+ * `2` Generate a chunked response if the server has returned HTTP/1.1 before
* `3` = Generate a chunked response if the client request is HTTP/1.1 and the origin server has returned HTTP/1.1 before
**Note:** If HTTP/1.1 is used, then Traffic Server can use keep-alive connections with pipelining to origin servers. If HTTP/0.9 is used, then Traffic Server does not use `keep-alive` connections to origin servers. If HTTP/1.0 is used, then Traffic Server can use `keep-alive` connections without pipelining to origin servers.
@@ -664,8 +664,12 @@
: Reloadable.
: When enabled (`1`), Traffic Server caches negative responses (such as `404 Not Found`) 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.
- **Note**: `Cache-Control` directives from the server forbidding cache are ignored for the following HTTP response codes, regardless of the value specified for the *`proxy.config.http.negative_caching_enabled`* variable. The following negative responses are cached by Traffic Server:
+ **Note**: `Cache-Control` directives from the server forbidding cache are ignored for the following HTTP response codes, regardless of the value specified for the *`proxy.config.http.negative_caching_enabled`* variable.
+ **Note**: If the origin response contains `Cache-Control` directives the response will be cached regardless of the value set in *`proxy.config.http.negative_caching_enabled`*
+
+ The following negative responses are cached by Traffic Server:
+
204 No Content
305 Use Proxy
400 Bad Request
@@ -906,7 +910,7 @@
**Note:** This option should only be enabled if you're having problems with caching *and* one of the following is true:
- * Your origin server sets `Vary: Accept` when doing content negotiation with `Accept` *OR*
+ * Your origin server sets `Vary: Accept` when doing content negotiation with `Accept` *OR*
* The server does not send a `406 (Not Acceptable)` response for types that it cannot serve.
@@ -1592,7 +1596,7 @@
: `STRING`
: Default: `NULL`
: The filename of the Traffic Server private key. Change this variable only if the private key is not located in the Traffic Server SSL client certificate file.
-
+
*`proxy.config.ssl.client.private_key.path`* {#proxy.config.ssl.client.private_key.path}
: `STRING`
: Default: `NULL`
@@ -1692,7 +1696,7 @@
*`proxy.config.plugin.plugin_dir`* {#proxy.config.plugin.plugin_dir}
: `STRING`
: Default: `libexec/trafficserver`
-: Specifies the location of Traffic Server plugins. This is based on
+: Specifies the location of Traffic Server plugins. This is based on
: your build environment, and options given to the configure script.
