[squid-users] Prepending a string to cache_peer username

[ngtech1ltd at gmail.com]

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

 

----

 <http://ngtech.co.il/main-en/> Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email:  <mailto:ngtech1ltd at gmail.com> ngtech1ltd at gmail.com



 

From: squid-users <squid-users-bounces at lists.squid-cache.org> On Behalf Of Charlie Orford
Sent: Monday, June 17, 2019 2:46 PM
To: squid-users at lists.squid-cache.org
Subject: [squid-users] 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20190618/fc5e7a3e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11295 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20190618/fc5e7a3e/attachment.png>