[squid-users] Possible to user reply_header_add directive with acl random access list ?

[--Ahmad--]

Alex .. indeed i asked many questions and you already solved me old issues . i do apologise for that Drop .
here is what we are going to achieve .


in simple :

i want to have external random addressees from list of addresses .
and in the same time i want a header like “start” header  who can be sent from squid to Host with tag.

say i have 10 ips 
i want random external over them .
and i want single  on each those 10 ips be sent back to Host.
if external was ip1 , then “start header” should be A
if external was ip2 , then “start header” should be b
if external was ip3 , then “start header” should be c
if external was ip4 , then “start header” should be d

and so on .


Thanks and again Guys you have been much helpful .


Thanks 


> On 19 Jul 2019, at 16:08, Alex Rousskov <rousskov at measurement-factory.com> wrote:
> 
> On 7/19/19 8:53 AM, --Ahmad-- wrote:
> 
>> is there any way can i let header acl stop on the 1st MATCH ?
> 
> Yes, your reply_header_add ACLs effectively stop on the first match,
> using the annotation trick. That part of your configuration is probably
> working. The primary problem is elsewhere.
> 
> 
>> do you have any other thing can we do to achieve what im looking for
>> based on my config below ?
> 
> FWIW, I do not know what you are looking for. I even checked earlier
> emails on this thread and could not find that information. Can you
> (re)state your goals using the following template?
> 
> "When Squid receives a client request with HTTP header X, I want Squid
> to forward that request using outgoing TCP address Y, and then add HTTP
> header Z to the response that Squid sends to the client."
> 
> Replace X, Y, and Z with your actual requirements. Adjust as needed,
> including removing any unnecessary parts.
> 
> Alex.