Re: [squid-users] Blocking or allowing specific arbitrary request headers in squid-3.1.

2010-03-17 Thread Graham Keeling
On Tue, Mar 16, 2010 at 09:46:44PM +, Amos Jeffries wrote: > On Tue, 16 Mar 2010 14:06:59 +, Graham Keeling > wrote: > > Hello, > > > > In older versions of squid, I was able to block or allow specific > arbitrary > > request headers. For example: > > > > header_access X-SomeRandomHeader

Re: [squid-users] Blocking or allowing specific arbitrary request headers in squid-3.1.

2010-03-16 Thread Henrik Nordström
tis 2010-03-16 klockan 21:46 + skrev Amos Jeffries: > Rant: I for one got tired of handling complaints because application X > would not work through Squid when the admin stripped away all it's > proprietary headers. Another Rant: Most admins I have spoken to which uses this say they do thi

Re: [squid-users] Blocking or allowing specific arbitrary request headers in squid-3.1.

2010-03-16 Thread Amos Jeffries
On Tue, 16 Mar 2010 14:06:59 +, Graham Keeling wrote: > Hello, > > In older versions of squid, I was able to block or allow specific arbitrary > request headers. For example: > > header_access X-SomeRandomHeaderA allow all > header_access X-SomeRandomHeaderB deny all > > In squid-3.1 (and 3

[squid-users] Blocking or allowing specific arbitrary request headers in squid-3.1.

2010-03-16 Thread Graham Keeling
Hello, In older versions of squid, I was able to block or allow specific arbitrary request headers. For example: header_access X-SomeRandomHeaderA allow all header_access X-SomeRandomHeaderB deny all In squid-3.1 (and 3.0, I think), the equivalent of header_access for request headers is now requ