Re: [squid-users] Configure squid 3.5 to use different parent proxies for different listening ports

On 21/02/2017 11:06 a.m., Damir Bagapov wrote: > > For some reason 'no-query originserver' version didn't work, so I had to > change it back to 'proxy-only default' HTTP has multiple different URI syntaxes for talking to proxies and origin servers. The specific details can be found at:

Re: [squid-users] Squid on separate box and it can't see packets

On 21/02/2017 10:25 a.m., Eliezer Croitoru wrote: > And just wanted to add a note that some Linux machines will act as an > HUB\BRIDGE by default in a similar scenario(will not drop > packets..). I noticed it while working on some tiny lab and it's > better to have the linux machine with ipv4_forw

Re: [squid-users] Configure squid 3.5 to use different parent proxies for different listening ports

Thanks for help, finally it seems to be working with following configuration http_port 3128 name=port_3128 http_port 3127 name=port_3127 nonhierarchical_direct off acl port_3128_acl myportname port_3128 acl port_3127_acl myportname port_3127 always_direct deny port_3128_acl always_direct deny p

Re: [squid-users] question about : NOTICE: Authentication not applicable onintercepted requests.

Hey, What you see is not a misconfiguration in the general meaning. Squid and any other proxy cannot authenticate without some kind of special tricks on an Intercept mode and port. There are products which offers transparently to hijack the web traffic and authenticate with the windows credentials

Re: [squid-users] Configure squid 3.5 to use different parent proxies for different listening ports

On 02/20/2017 02:08 PM, Damir Bagapov wrote: > I need to configure squid in a way when all incoming requests to > 3128 port will be redirected to proxy1 (as it works now), and all > incoming requests to 3127 will be redirected to proxy2. > http_port 3128 > http_port 3127 > > acl port_3128 port 3

Re: [squid-users] Squid on separate box and it can't see packets

And just wanted to add a note that some Linux machines will act as an HUB\BRIDGE by default in a similar scenario(will not drop packets..). I noticed it while working on some tiny lab and it's better to have the linux machine with ipv4_forward turned on with an iptables DROP rule rather then wit

Re: [squid-users] Configure squid 3.5 to use different parent proxies for different listening ports

And forgot to add also: nonhierarchical_direct off Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: elie...@ngtech.co.il -Original Message- From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf Of Eliezer Croitoru Sent: Monday, Feb

Re: [squid-users] Configure squid 3.5 to use different parent proxies for different listening ports

You can try the next: http_port 3128 name=one http_port 3127 name=two acl port_3128 myportname one acl port_3127 myportname two always_direct deny port_3128 always_direct deny port_3127 never_direct allow port_3128 never_direct allow port_3127 # 3128 cache_peer proxy01 parent 3128 0 no-query o

[squid-users] Configure squid 3.5 to use different parent proxies for different listening ports

Hi, I have following configuration: # Squid normally listens to port 3128 http_port 3128 cache_peer proxy1_address parent proxy1_port 0 proxy-only default login=name1:pass1 never_direct allow all And I need to configure squid in a way when all incoming requests to 3128 port will be redirected t

[squid-users] Configure squid 3.5 to use different parent proxies for different listening ports

Hi, I have following configuration: # Squid normally listens to port 3128 http_port 3128 cache_peer proxy1_address parent proxy1_port 0 proxy-only default login=name1:pass1 never_direct allow all And I need to configure squid in a way when all incoming requests to 3128 port will be redirected t