comparison xml/en/docs/http/ngx_http_proxy_module.xml @ 504:695f83494c19

Emphasized on what the "updating" parameter of the "proxy_cache_use_stale" directive achieves. Referenced the "proxy_cache_lock" directive from there, which has similar effect when populating a new cache element.
author Ruslan Ermilov <ru@nginx.com>
date Tue, 24 Apr 2012 06:54:47 +0000
parents cbc2d1b51cb6
children 657848837328
comparison
equal deleted inserted replaced
503:aed015c3dedd 504:695f83494c19
312 If an error occurs while working with the proxied server it is possible 312 If an error occurs while working with the proxied server it is possible
313 to use a stale cached response. 313 to use a stale cached response.
314 This directives determines in which cases it is permitted. 314 This directives determines in which cases it is permitted.
315 The directive’s parameters match those of the 315 The directive’s parameters match those of the
316 <link id="proxy_next_upstream"/> directive. 316 <link id="proxy_next_upstream"/> directive.
317 </para>
318
319 <para>
317 Additionally, the <literal>updating</literal> parameter permits 320 Additionally, the <literal>updating</literal> parameter permits
318 to use a stale cached response if it is currently being updated. 321 to use a stale cached response if it is currently being updated.
322 This allows to minimize the number of accesses to proxied servers
323 when updating cached data.
324 </para>
325
326 <para>
327 To minimize the number of accesses to proxied servers when
328 populating a new cache element, the <link id="proxy_cache_lock"/>
329 directive can be used.
319 </para> 330 </para>
320 331
321 </directive> 332 </directive>
322 333
323 334