Re: [squid-users] Why doesn't REQUEST_HEADER_ACCESS work properly with aclnames?

On 21/04/11 13:04, Jenny Lee wrote:
>
>>> I have 3.2.0.1 and unfortunately this does not work either. I
>>> will check on 3.2.0.7 (would that make a difference?).
>>
>> May do. I don't recall changing anything there directly but the
>> passing around of request details has been fixed in a few places
>> earlier which may affect it.
>>
>> Also, do you have this part which I forgot to add? cache_peer ....
>> name=X
>
> Yes I do, Amos.
>
<snip wishlist>
>
> Here what I am trying to do is to brand our connections. Suppose we
> have a crawler. It would be nice if the crawler identified itself as
> such. On the other hand, I do not want to modify the UA of our OFFICE
> users. They should be passed as is.

I'm a little confused by this scenario and your statement "It would be
nice if the crawler identified itself".
  Is it spoofing an agent name identical that on your OFFICE machines?
Even the absence of a U-A header is identification in a way.

>
> I thought this would be relatively easy to accomplish in squid, after
> all it is very able and comes with the whole shabang and the kitchen
> sink, but unfortunately i have had no success so far.

AFAIK it *should* only require that config you have. If we can figure
out whats going wrong the bug can be fixed.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.12
   Beta testers wanted for 3.2.0.7 and 3.1.12.1