Squid configuration directive refresh_stale_hit

Available in: 2.7   2.HEAD   2.6  

History:

Changes in 2.6 refresh_stale_hit

New directive similar to collapsed_forwarding and activates an alternative optimized request processing when there is very many concurrent requests for the same recently expired URL.

Configuration Details:

Option Name:refresh_stale_hit
Replaces:
Requires:
Default Value:refresh_stale_hit 0 seconds
Suggested Config: 


	This option changes the refresh algorithm to allow concurrent
	requests while an object is being refreshed to be processed as
	cache hits if the object expired less than X seconds ago. Default
	is 0 to disable this feature. This option is mostly interesting
	in accelerator setups where a few objects is accessed very
	frequently.
 

Back

Search

 

Introduction

Documentation

Support

Miscellaneous

Web Site Translations

Mirrors