# HG changeset patch # User Vladimir Homutov # Date 1385983491 -14400 # Node ID e582a10b19179b17500075d25204b79f7c5178b0 # Parent dd64ce140de23fd3ab9bba526fe15b0877509d94 Documented the "proxy_cache_purge" and "fastcgi_cache_purge" directives. diff -r dd64ce140de2 -r e582a10b1917 xml/en/docs/http/ngx_http_fastcgi_module.xml --- a/xml/en/docs/http/ngx_http_fastcgi_module.xml Wed Oct 23 13:36:17 2013 +0400 +++ b/xml/en/docs/http/ngx_http_fastcgi_module.xml Mon Dec 02 15:24:51 2013 +0400 @@ -10,7 +10,7 @@ + rev="13">
@@ -368,6 +368,58 @@ + +string ... + +http +server +location +1.5.7 + + +Defines conditions under which the request will be considered a cache +purge request. +If at least one value of the string parameters is not empty and is not equal +to “0” then the cache entry with a corresponding +cache key is removed. +The result of successful operation is indicated by returning +the response. + + + +If the cache key of a purge request ends +with an asterisk (“*”), all cache entries matching the +wildcard key will be removed from the cache. + + + +Example configuration: + +fastcgi_cache_path /data/nginx/cache keys_zone=cache_zone:10m; + +map $request_method $purge_method { + PURGE 1; + default 0; +} + +server { + ... + location / { + fastcgi_pass backend; + fastcgi_cache cache_zone; + fastcgi_cache_key $uri; + fastcgi_cache_purge $purge_method; + } +} + + +This functionality is available as part of our only. + + + + + + on | off off diff -r dd64ce140de2 -r e582a10b1917 xml/en/docs/http/ngx_http_proxy_module.xml --- a/xml/en/docs/http/ngx_http_proxy_module.xml Wed Oct 23 13:36:17 2013 +0400 +++ b/xml/en/docs/http/ngx_http_proxy_module.xml Mon Dec 02 15:24:51 2013 +0400 @@ -10,7 +10,7 @@ + rev="17">
@@ -366,6 +366,58 @@ + +string ... + +http +server +location +1.5.7 + + +Defines conditions under which the request will be considered a cache +purge request. +If at least one value of the string parameters is not empty and is not equal +to “0” then the cache entry with a corresponding +cache key is removed. +The result of successful operation is indicated by returning +the response. + + + +If the cache key of a purge request ends +with an asterisk (“*”), all cache entries matching the +wildcard key will be removed from the cache. + + + +Example configuration: + +proxy_cache_path /data/nginx/cache keys_zone=cache_zone:10m; + +map $request_method $purge_method { + PURGE 1; + default 0; +} + +server { + ... + location / { + proxy_pass http://backend; + proxy_cache cache_zone; + proxy_cache_key $uri; + proxy_cache_purge $purge_method; + } +} + + +This functionality is available as part of our only. + + + + + + on | off off