On 11/18/2015 12:53 AM, Tarik Demirci wrote:
> I did more detailed tests for this case. Constructing a tcp-in-https
> connection results with error ERR_PROTOCOL_UNKNOWN in spite of
> "on_unsupported_protocol tunnel all" conf directive. Is this a Squid
> bug? Doc for on_unsupported_protocol says
On 14/11/2015 8:55 a.m., Amos Jeffries wrote:
> On 14/11/2015 8:40 a.m., Yuri Voinov wrote:
>>
>> Netcat plaintext is not HTTPS :) Also via 443 port :)
>>
>
> Thanks Yuri. Can't believe I missed that bit :-0
>
> Amos
>
>> 14.11.15 1:26, Amos Jeffries пишет:
>>> On 13/11/2015 10:00 p.m., Tarik
Hi,
Did anyone try on_unsupported_protocol for bumped https connections? I
made a simple test with netcat but test failed. Same test is
successful for port 80 (also intercepted by squid).
Netcat Server --- Squid Box --- Client
On Client:
echo "" | nc 10.50.13.1 443
***
On Netcat Server:
On 13/11/2015 10:00 p.m., Tarik Demirci wrote:
> Hi,
> Did anyone try on_unsupported_protocol for bumped https connections? I
> made a simple test with netcat but test failed. Same test is
> successful for port 80 (also intercepted by squid).
HTTPS is a supported protocol.
Amos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Netcat plaintext is not HTTPS :) Also via 443 port :)
14.11.15 1:26, Amos Jeffries пишет:
> On 13/11/2015 10:00 p.m., Tarik Demirci wrote:
>> Hi,
>> Did anyone try on_unsupported_protocol for bumped https connections? I
>> made a simple test with
On 14/11/2015 8:40 a.m., Yuri Voinov wrote:
>
> Netcat plaintext is not HTTPS :) Also via 443 port :)
>
Thanks Yuri. Can't believe I missed that bit :-0
Amos
> 14.11.15 1:26, Amos Jeffries пишет:
>> On 13/11/2015 10:00 p.m., Tarik Demirci wrote:
>>> Hi,
>>> Did anyone try
