Hi.
On 16.11.2015 0:39, Alex Rousskov wrote:
> On 11/15/2015 12:03 PM, Eugene M. Zheganin wrote:
>> It's not even a HTTPS, its a tunneled HTTP CONNECT. But
>> squid for some reason thinks there shoudl be a HTTPS inside.
> Hello Eugene,
>
> Squid currently supports two kinds of CONNECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
17.11.15 15:46, Christos Tsantilas пишет:
> On 11/16/2015 08:00 AM, Eugene M. Zheganin wrote:
>> Hi.
>>
>> On 16.11.2015 00:14, Yuri Voinov wrote:
>>
>>> It's common knowledge. Squid is unable to pass an unknown protocol on
>>> the standard
On 11/16/2015 08:00 AM, Eugene M. Zheganin wrote:
Hi.
On 16.11.2015 00:14, Yuri Voinov wrote:
It's common knowledge. Squid is unable to pass an unknown protocol on
the standard port. Consequently, the ability to proxy this protocol does
not exist.
If it was simply a tunneling ... It is not
On 11/15/2015 11:13 PM, Eugene M. Zheganin wrote:
> On 16.11.2015 00:39, Alex Rousskov wrote:
>> Squid currently supports two kinds of CONNECT tunnels:
>>
>> 1. A regular opaque tunnel, as intended by HTTP specifications.
>>
>> 2. An inspected tunnel containing SSL/TLS-encrypted HTTP traffic.
16.11.15 12:00, Eugene M. Zheganin пишет:
Hi.
On 16.11.2015 00:14, Yuri Voinov wrote:
It's common knowledge. Squid is unable to pass an unknown protocol on
the standard port. Consequently, the ability to proxy this protocol does
not exist.
If it was simply a tunneling ... It is not https.
On 11/15/2015 12:03 PM, Eugene M. Zheganin wrote:
> It's not even a HTTPS, its a tunneled HTTP CONNECT. But
> squid for some reason thinks there shoudl be a HTTPS inside.
Hello Eugene,
Squid currently supports two kinds of CONNECT tunnels:
1. A regular opaque tunnel, as intended by HTTP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
16.11.15 1:39, Alex Rousskov пишет:
> On 11/15/2015 12:03 PM, Eugene M. Zheganin wrote:
>> It's not even a HTTPS, its a tunneled HTTP CONNECT. But
>> squid for some reason thinks there shoudl be a HTTPS inside.
>
>
> Hello Eugene,
>
> Squid
On 11/15/2015 01:00 PM, Yuri Voinov wrote:
> 16.11.15 1:39, Alex Rousskov пишет:
>> Squid currently supports two kinds of CONNECT tunnels:
>> 1. A regular opaque tunnel, as intended by HTTP specifications.
>> 2. An inspected tunnel containing SSL/TLS-encrypted HTTP traffic.
>> Opaque
Hi.
On 16.11.2015 00:14, Yuri Voinov wrote:
> It's common knowledge. Squid is unable to pass an unknown protocol on
> the standard port. Consequently, the ability to proxy this protocol does
> not exist.
>
> If it was simply a tunneling ... It is not https. And not just
> HTTP-over-443. This is
Hi.
On 15.11.2015 0:43, Walter H. wrote:
> On 13.11.2015 14:53, Yuri Voinov wrote:
>> There is no solution for ICQ with Squid now.
>>
>> You can only bypass proxying for ICQ clients.
> from where do the ICQ clients get the trusted root certificates?
> maybe this is the problem, that e.g. the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-ICQ-contest-td4673938.html
16.11.15 1:03, Eugene M. Zheganin пишет:
> Hi.
>
> On 15.11.2015 0:43, Walter H. wrote:
>> On 13.11.2015 14:53, Yuri Voinov wrote:
>>> There is no solution for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It's common knowledge. Squid is unable to pass an unknown protocol on
the standard port. Consequently, the ability to proxy this protocol does
not exist.
If it was simply a tunneling ... It is not https. And not just
HTTP-over-443. This is more
Hi.
On 13.11.2015 18:53, Yuri Voinov wrote:
> There is no solution for ICQ with Squid now.
>
> You can only bypass proxying for ICQ clients.
>
There is: I can disable sslBump, and I did it already. It doesn't look
production-ready anyway.
Eugene.
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This will decrease request hit ratio minimum at 50%
14.11.15 20:11, Eugene M. Zheganin пишет:
> Hi.
>
> On 13.11.2015 18:53, Yuri Voinov wrote:
>> There is no solution for ICQ with Squid now.
>>
>> You can only bypass proxying for ICQ clients.
>>
On 13.11.2015 14:53, Yuri Voinov wrote:
There is no solution for ICQ with Squid now.
You can only bypass proxying for ICQ clients.
from where do the ICQ clients get the trusted root certificates?
maybe this is the problem, that e.g. the squid CA cert is only installed
in FF
and nowhere else
Hi.
Today I discovered that a bunch of old legacy ICQ clients that some
people till use have lost the ability to use HTTP CONNECT tunneling with
sslBump. No matter what I tried to allow direct splicing for them, all
was useless:
- arranging them by dst ACL, and splicing that ACL
- arranging them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
There is no solution for ICQ with Squid now.
You can only bypass proxying for ICQ clients.
13.11.15 14:41, Eugene M. Zheganin пишет:
> Hi.
>
> Today I discovered that a bunch of old legacy ICQ clients that some
> people till use have lost the
17 matches
Mail list logo
