Squid configuration directive send_hit

Available in: 4   3.5  


Changes to send_hit in Squid-3.5:

New configuration directive to enable/disable sending cached content based on ACL selection. ACL can be based on client request or cached response details.

This directive is not available in the 3.4 version of Squid.

For older versions than 3.3 see the linked pages above

Configuration Details:

Option Name:send_hit
Default Value:By default, this directive is unused and has no effect.
Suggested Config:

	Responses denied by this directive will not be served from the cache
	(but may still be cached, see store_miss). This directive has no
	effect on the responses it allows and on the cached objects.

	Please see the "cache" directive for a summary of differences among
	store_miss, send_hit, and cache directives.

	Unlike the "cache" directive, send_hit only supports fast acl
	types.  See http://wiki.squid-cache.org/SquidFaq/SquidAcl for details.

	For example:

		# apply custom Store ID mapping to some URLs
		acl MapMe dstdomain .c.example.com
		store_id_program ...
		store_id_access allow MapMe

		# but prevent caching of special responses
		# such as 302 redirects that cause StoreID loops
		acl Ordinary http_status 200-299
		store_miss deny MapMe !Ordinary

		# and do not serve any previously stored special responses
		# from the cache (in case they were already cached before
		# the above store_miss rule was in effect).
		send_hit deny MapMe !Ordinary








Web Site Translations