Re: [squid-users] squidclient and PROXY procotol enabled http_port (solved)

2018-04-17 Thread Rafael Akchurin
Hello Amos, Eliezer and all, Thanks a lot for your ideas/suggestions. Decided to go easy way: - added another "http_port 127.0.0.1:3128" directive to squid.conf (without require-proxy-header option) - directed squidclient binary to use it Hope no side effects from this configu

Re: [squid-users] squidclient and PROXY procotol enabled http_port

2018-04-14 Thread Eliezer Croitoru
, April 14, 2018 11:14 To: squid-users (squid-users@lists.squid-cache.org) Subject: [squid-users] squidclient and PROXY procotol enabled http_port Greetings to everyone, I have the following deployment: - Several Squid nodes configured with "http_port 3128 require-proxy-h

Re: [squid-users] squidclient and PROXY procotol enabled http_port

2018-04-14 Thread Amos Jeffries
On 14/04/18 20:13, Rafael Akchurin wrote: > Question > > Is it possible to ask squidclient to prepend the PROXY header to its request? > It should be relatively easy to add, but has not been coded yet if thats what you mean. Patches welcome. Amos

[squid-users] squidclient and PROXY procotol enabled http_port

2018-04-14 Thread Rafael Akchurin
Greetings to everyone, I have the following deployment: - Several Squid nodes configured with "http_port 3128 require-proxy-header" - One haproxy what relays TCP connections to nodes - squidclient that is run on each node manually Browsers pointing to haproxy are corre