The SQUID-211-Skype_groups_and_msnp_bypass-t11.patch applied to trunk as
r14913
The SQUID-211-FwdState_connectStart_cleanup-t1.patch patch applied as r14914
The final applied patch has one more change over the t10 patch, it
merges the ConnStateData::startPeekAndSplice() and
On 2/11/2016 4:31 a.m., Christos Tsantilas wrote:
> On 10/28/2016 01:11 PM, Amos Jeffries wrote:
>> On 21/10/2016 3:55 a.m., Christos Tsantilas wrote:
>>>
>>> Support tunneling of bumped non-HTTP traffic. Other SslBump fixes.
>>>
>>> Use case: Skype groups appear to use TLS-encrypted MSNP protocol
On 10/28/2016 01:11 PM, Amos Jeffries wrote:
On 21/10/2016 3:55 a.m., Christos Tsantilas wrote:
Support tunneling of bumped non-HTTP traffic. Other SslBump fixes.
Use case: Skype groups appear to use TLS-encrypted MSNP protocol instead
of HTTPS. This change allows Squid admins using SslBump
On 29/10/2016 4:07 a.m., Alex Rousskov wrote:
> On 10/28/2016 07:54 AM, Christos Tsantilas wrote:
>> On 10/28/2016 01:11 PM, Amos Jeffries wrote:
>>> On 21/10/2016 3:55 a.m., Christos Tsantilas wrote:
Support tunneling of bumped non-HTTP traffic. Other SslBump fixes.
>
>>> Are any of these
On 10/28/2016 07:54 AM, Christos Tsantilas wrote:
> On 10/28/2016 01:11 PM, Amos Jeffries wrote:
>> On 21/10/2016 3:55 a.m., Christos Tsantilas wrote:
>>> Support tunneling of bumped non-HTTP traffic. Other SslBump fixes.
>> Are any of these additional fixes able to be easily broken out into
>>
On 10/28/2016 01:11 PM, Amos Jeffries wrote:
On 21/10/2016 3:55 a.m., Christos Tsantilas wrote:
Support tunneling of bumped non-HTTP traffic. Other SslBump fixes.
Use case: Skype groups appear to use TLS-encrypted MSNP protocol instead
of HTTPS. This change allows Squid admins using SslBump
On 21/10/2016 3:55 a.m., Christos Tsantilas wrote:
>
> Support tunneling of bumped non-HTTP traffic. Other SslBump fixes.
>
> Use case: Skype groups appear to use TLS-encrypted MSNP protocol instead
> of HTTPS. This change allows Squid admins using SslBump to tunnel Skype
> groups and similar
I am attaching new patch.
On 10/19/2016 07:13 PM, Alex Rousskov wrote:
On 10/19/2016 08:49 AM, Christos Tsantilas wrote:
I am attaching a new patch.
I would like to discuss two issues:
* Logging of scheme-less URLs
This is defines a new proto the PROTO_TCP, and for this prints the url
On 10/19/2016 07:13 PM, Alex Rousskov wrote:
On 10/19/2016 08:49 AM, Christos Tsantilas wrote:
I am attaching a new patch.
I would like to discuss two issues:
* Logging of scheme-less URLs
This is defines a new proto the PROTO_TCP, and for this prints the url
in the form host:port.
The
On 10/19/2016 08:49 AM, Christos Tsantilas wrote:
> I am attaching a new patch.
I would like to discuss two issues:
* Logging of scheme-less URLs
> This is defines a new proto the PROTO_TCP, and for this prints the url
> in the form host:port.
The PROTO_TCP name sounds bad because we may want
I am attaching a new patch.
This is defines a new proto the PROTO_TCP, and for this prints the url
in the form host:port.
There are no other changes from t8 patch.
On 10/18/2016 08:52 AM, Alex Rousskov wrote:
On 10/17/2016 10:56 PM, Amos Jeffries wrote:
On 18/10/2016 7:54 a.m., Christos
On 10/17/2016 10:56 PM, Amos Jeffries wrote:
> On 18/10/2016 7:54 a.m., Christos Tsantilas wrote:
>> On 10/17/2016 05:42 PM, Alex Rousskov wrote:
>>> On 10/17/2016 01:57 AM, Christos Tsantilas wrote:
On 10/14/2016 02:30 PM, Marcus Kool wrote:
> Squid sends the following line to the URL
On 18/10/2016 7:54 a.m., Christos Tsantilas wrote:
> On 10/17/2016 05:42 PM, Alex Rousskov wrote:
>> On 10/17/2016 01:57 AM, Christos Tsantilas wrote:
>>> On 10/14/2016 02:30 PM, Marcus Kool wrote:
Squid sends the following line to the URL rewriter:
(unknown)://173.194.76.188:443 / -
On 10/17/2016 05:42 PM, Alex Rousskov wrote:
On 10/17/2016 01:57 AM, Christos Tsantilas wrote:
On 10/14/2016 02:30 PM, Marcus Kool wrote:
Squid sends the following line to the URL rewriter:
(unknown)://173.194.76.188:443 / - NONE
Squid generates internally request to serve the non-HTTP
On 10/14/2016 02:30 PM, Marcus Kool wrote:
I started testing this patch and observed one unwanted side effect of
this patch:
When a client connects to mtalk.google.com,
Squid sends the following line to the URL rewriter:
(unknown)://173.194.76.188:443 / - NONE
Thank you.
I should have refer on
I started testing this patch and observed one unwanted side effect of
this patch:
When a client connects to mtalk.google.com,
Squid sends the following line to the URL rewriter:
(unknown)://173.194.76.188:443 / - NONE
Marcus
Quoting Christos Tsantilas :
Use case: Skype
16 matches
Mail list logo