Re: Prepending a string to cache_peer username

[<ngtech1ltd@xxxxxxxxx>]

I believe that eCAP or ICAP can do the trick for you.

However I am not sure if it’s a good thing to pass usernames and password in WWW Http requests.

 

Eliezer

 

----

Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: ngtech1ltd@xxxxxxxxx

 

From: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> On Behalf Of Charlie Orford
Sent: Monday, June 17, 2019 2:46 PM
To: squid-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Prepending a string to cache_peer username

 

Annoyingly, one of our upstream cache_peers requires a fixed string to be prepended to client usernames.

I'm aware the login= option for cache_peer allows substituting * with client provided username and appending a fixed string to this.

Is there a way to achieve something similar if we need to prepend rather than append a string (perhaps a clever ACL/external_auth trick we could use to modify client usernames destined for this peer)?

Thanks for any suggestions.

_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users