Squid configuration directive reply_header_add

Available in: 4  

History:

Changes to reply_header_add in Squid-4:

New directive to add header fields to outgoing HTTP responses to the client.

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

For older versions than 3.3 see the linked pages above

Configuration Details:

Option Name:reply_header_add
Replaces:
Requires:
Default Value:none
Suggested Config:

	Usage:   reply_header_add field-name field-value [ acl ... ]
	Example: reply_header_add X-Client-CA "CA=%ssl::>cert_issuer" all

	This option adds header fields to outgoing HTTP responses (i.e., response
	headers delivered by Squid to the client). This option has no effect on
	cache hit detection. The equivalent adaptation vectoring point in
	ICAP terminology is post-cache RESPMOD. This option does not apply to
	successful CONNECT replies.

	Field-name is a token specifying an HTTP header name. If a
	standard HTTP header name is used, Squid does not check whether
	the new header conflicts with any existing headers or violates
	HTTP rules. If the response to be modified already contains a
	field with the same name, the old field is preserved but the
	header field values are not merged.

	Field-value is either a token or a quoted string. If quoted
	string format is used, then the surrounding quotes are removed
	while escape sequences and %macros are processed.

	One or more Squid ACLs may be specified to restrict header
	injection to matching responses. As always in squid.conf, all
	ACLs in the ACL list must be satisfied for the insertion to
	happen. The reply_header_add option supports fast ACLs only.

	See also: request_header_add.

 

Back

 

Introduction

Documentation

Support

Miscellaneous

Web Site Translations

Mirrors