[squid-users] Prepending a string to cache_peer username

[Charlie Orford]

On 18/06/2019 06:01, ngtech1ltd at gmail.com wrote:
>
> 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
>
> *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.
>


Thanks Eliezer. ICAP looks interesting. Do you know for sure if Squid's 
cache_peer code would indeed use the username from a modified 
Proxy-Authorization header rather than the initial authenticated 
username provided when the client originally connected to Squid (made 
available to ICAP via adaptation_send_username)?