1 commit 6648ff0cccee04a6a0c0e64050151b5d6c5bac51
2 Author: Jarno Huuskonen <jarno.huuskonen@uef.fi>
3 Date: Fri Jan 4 14:05:02 2019 +0200
5 DOC: http-request cache-use / http-response cache-store expects cache name
7 Adds missing cache name option to http-request cache-use and
8 http-response cache-store documentation.
10 Also adds optional if/unless condition to
11 10.2.2. Proxy section: http-request cache-use / http-response cache-store
13 (cherry picked from commit 251a6b72a8b6f0a4b167f6a2960e422d682aed80)
14 Signed-off-by: Willy Tarreau <w@1wt.eu>
15 (cherry picked from commit 5376f6af9239fdf8a79b6c912387de12e3c9d6cd)
16 [wla: no http-request/response section in 1.8]
17 Signed-off-by: William Lallemand <wlallemand@haproxy.org>
19 diff --git a/doc/configuration.txt b/doc/configuration.txt
20 index 4f999e25..712e56e2 100644
21 --- a/doc/configuration.txt
22 +++ b/doc/configuration.txt
23 @@ -17157,13 +17157,13 @@ max-age <seconds>
27 -http-request cache-use <name>
28 +http-request cache-use <name> [ { if | unless } <condition> ]
29 Try to deliver a cached object from the cache <name>. This directive is also
30 mandatory to store the cache as it calculates the cache hash. If you want to
31 use a condition for both storage and delivering that's a good idea to put it
34 -http-response cache-store <name>
35 +http-response cache-store <name> [ { if | unless } <condition> ]
36 Store an http-response within the cache. The storage of the response headers
37 is done at this step, which means you can use others http-response actions
38 to modify headers before or after the storage of the response. This action