Re: [squid-users] Squid Listening on many ports

On 18/06/19 8:33 am, johnr wrote: > Hi, > > I am wanting to run squid listening on many ports (~100-200). From prior > mailing list questions > (http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-with-multiple-ips-is-listenting-to-some-ips-with-port-and-not-all-of-ips-td4668784.html), > I se

Re: [squid-users] Prepending a string to cache_peer username

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:

[squid-users] Squid Listening on many ports

Hi, I am wanting to run squid listening on many ports (~100-200). From prior mailing list questions (http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-with-multiple-ips-is-listenting-to-some-ips-with-port-and-not-all-of-ips-td4668784.html), I see how this is possible. But, I was curious abo

[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