[squid-users] Redirect request to cache_peer using username and passwords
premchand142 at gmail.com
Thu Jul 2 12:59:19 UTC 2020
Thanks for the response.
However, what do you want to happen when that user's dedicated peer is
Can it be routed to another peer if a dedicated peer is unavailable?
because each peer is accessed by a different username and password. If
there is an option to route then I will keep a backup peer(Peer4) so if any
one of the peers(Peer1,Peer2,Peer3) is unavailable it can route to the
backup peer and once the unavailable peer become available then traffic
should auto route to them from backup peer.
If there is no option that fits as I explained above then I want to stop
all access for them.
Are you wanting to keep this behaviour?
I don't want to use the round-robin behaviour. I want to route requests to
On Thu, Jul 2, 2020 at 3:19 PM Prem Chand <premchand142 at gmail.com> wrote:
> I need to redirect my clients requests to different Cache_peers using
> username and passwords through my proxy. Below is the rough sketch. Can
> someone suggest to me how I can achieve this?
> Client1(Username1:password1) ->Proxy:443 -> Cache_peer:3218
> Client 2(Username2:password2)->Proxy:443-> Cache_peer:3219
> This is my current configuration, I'm doing round robin through
> cache_peers when authenticated with a single username and password in
> /etc/squid/squidpasswdfile file
> auth_param basic program /usr/lib64/squid/ncsa_auth
> auth_param basic realm proxy
> acl auth_users proxy_auth REQUIRED
> http_access allow auth_users
> http_access deny all
> cache_peer Peer1 parent 3218 0 round-robin no-query weight=1
> cache_peer Peer2 parent 3219 0 round-robin no-query weight=1
> cache_peer Peer3 parent 3219 0 round-robin no-query weight=1
> Thanks & Regards
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squid-users