[Devil-Linux-discuss] squid_compile_option_changed?

[Oliver N. <dig...@gm...>]

Hi!

Yesterday i made a new build from DL-1.3.6 and after starting up my 
system i saw some squid errors:

-->
src@devil (squid): cache_cf.cc(346) squid.conf:2532 unrecognized: ' 
       header_access'
<--

After investigating the squid.conf file i found out that the 
header_access feature caused the problem.
I use this feature to do some basic header filtering.
It worked before, so i think the compile option for
squid has changed.
To use the header_access functionality the option:
--enable-http-violations has to be set.
A /usr/sbin/squid -v shows that this option was not set.

My question now is:
Was this option removed by mistake, or are there other reasons to change 
that?

Oliver











> Option Name:	header_access
> Replaces:	
> Requires:	--enable-http-violations
> Default Value:	none
> Suggested Config: 	
> 
> 	Usage: header_access header_name allow|deny [!]aclname ...
> 
> 	WARNING: Doing this VIOLATES the HTTP standard.  Enabling
> 	this feature could make you liable for problems which it
> 	causes.
> 
> 	This option replaces the old 'anonymize_headers' and the
> 	older 'http_anonymizer' option with something that is much
> 	more configurable. This new method creates a list of ACLs
> 	for each header, allowing you very fine-tuned header
> 	mangling.
> 
> 	You can only specify known headers for the header name.
> 	Other headers are reclassified as 'Other'. You can also
> 	refer to all the headers with 'All'.
> 
> 	For example, to achieve the same behavior as the old
> 	'http_anonymizer standard' option, you should use:
> 
> 		header_access From deny all
> 		header_access Referer deny all
> 		header_access Server deny all
> 		header_access User-Agent deny all
> 		header_access WWW-Authenticate deny all
> 		header_access Link deny all