Squid configuration directive request_header_replace

Available in: 3.3   3.2   3.1   3.HEAD  

History:

Changes in 3.2 request_header_replace

Added support for custom request header names.

Changes in 3.1 request_header_replace

This option allows you to change the contents of request headers. 

        To be consistent with the naming changes of header_access in Squid 3
        (header_access has been split into two options request_header_access
        and reply_header_access), header_replace (now deprecated) is being
        replaced by request_header_replace.

Configuration Details:

Option Name:request_header_replace
Replaces:header_replace
Requires:--enable-http-violations
Default Value:none
Suggested Config: 


	Usage:   request_header_replace header_name message
	Example: request_header_replace User-Agent Nutscrape/1.0 (CP/M; 8-bit)

	This option allows you to change the contents of headers
	denied with request_header_access above, by replacing them
	with some fixed string. This replaces the old fake_user_agent
	option.

	This only applies to request headers, not reply headers.

	By default, headers are removed if denied.
 

Back

Search

 

Introduction

Documentation

Support

Miscellaneous

Web Site Translations

Mirrors