Re: Filtering Accept-Encoding header ?

On Nov 17, 6:09pm, Henrik Nordstrom (possibly) wrote:
> Andreas Jung wrote:
>
> > Maybe we'll see a possibily in a future release of Squid to configure
> > the headers of the http_anonymizer option !?
>
> If you (or someone else) code it up and send it as a patch to
> squid-bugs@ircache.net then I think that it will be accepted.
>
> Don't expect one of the main developers to look into this any
> time soon. The anonymizer is against the religion of most Squid
> developers (changes the HTTP message in ways not permitted by
> the HTTP specification).

>From looking over the HTTP specifications, it's actually allowed for a
non-transparent proxy to do things like this, and anonymization is
specifically mentioned as an application for a non-transparent
proxy. There are various things regarding warning headers; I have
consequently coded (but have not yet tested) a httpHeaderAddWarning
subroutine, which takes care of doing things like adding in the
hostname to the middle. With such, there are a lot of alterations to
the HTTP headers that the HTTP 1.1 specifications allow. (Actually,
there's one such alteration that the specs _require_ that squid
doesn't do (except in my patched version) - namely inserting a Date:
header if one isn't present.

        -Allen

P.S. I am currently looking at coding specific header deletion via
acls; if anyone else is interested in this, please contact me, as I'd
be very happy to offload some of the work (and the testing) to others
- this isn't my main job. I am specifically _not_ interested in
helping people make squid into censorware, so I'm not going to be
working on any block-after-retrieve code.

-- 
Allen Smith				easmith@beatrice.rutgers.edu