Re: [squid-users] tcp_outgoing_address and HTTPS

2018-03-20 Thread Amos Jeffries
On 21/03/18 08:12, Michael Pro wrote: > Totally agree with you, and at the same time - do not agree. But, > consider the following situation. There is https://site.net/ where > there is 1.jpg and 2.jpg. If I download from this site 1.jpg from the > address 1.1.1.1 and 2.jpg from the address 2.2.2.2

Re: [squid-users] tcp_outgoing_address and HTTPS

2018-03-20 Thread Alex Rousskov
On 03/20/2018 01:12 PM, Michael Pro wrote: > Totally agree with you, and at the same time - do not agree. AFAICT, I only stated facts, not opinions. There is nothing to agree or disagree with in my response. Alex. ___ squid-users mailing list squid-user

Re: [squid-users] tcp_outgoing_address and HTTPS

2018-03-20 Thread Michael Pro
Totally agree with you, and at the same time - do not agree. But, consider the following situation. There is https://site.net/ where there is 1.jpg and 2.jpg. If I download from this site 1.jpg from the address 1.1.1.1 and 2.jpg from the address 2.2.2.2. Even more. There are situations when you nee

Re: [squid-users] tcp_outgoing_address and HTTPS

2018-03-20 Thread Alex Rousskov
On 03/20/2018 05:11 AM, Michael Pro wrote: > Question: how can we break the established channel (unpinn it) along > the old route and establish a new channel along the new route, when we > already know how. Squid supports using multiple sequential connections for the same from-client request, but

Re: [squid-users] tcp_outgoing_address and HTTPS

2018-03-20 Thread Amos Jeffries
On 21/03/18 00:11, Michael Pro wrote: > squid-5 master branch, not have personal/private repository changes, > not use cache_peer's ability, (if it's matters - not use transparent > proxying ability). > > We have a set of rules (ACL's with url regex) for content, depending > on which we make a d

[squid-users] tcp_outgoing_address and HTTPS

2018-03-20 Thread Michael Pro
squid-5 master branch, not have personal/private repository changes, not use cache_peer's ability, (if it's matters - not use transparent proxying ability). We have a set of rules (ACL's with url regex) for content, depending on which we make a decision for the outgoing address, for example, fro