On 29/06/2015 12:12 a.m., Amos Jeffries wrote:
> On 24/06/2015 3:26 a.m., Alex Rousskov wrote:
>> On 06/19/2015 06:46 PM, Amos Jeffries wrote:
>>> On 20/06/2015 4:54 a.m., Alex Rousskov wrote:
Hello,
The attached trunk patch fixes a rare but nasty problem by removing
a very
On 24/06/2015 3:26 a.m., Alex Rousskov wrote:
> On 06/19/2015 06:46 PM, Amos Jeffries wrote:
>> On 20/06/2015 4:54 a.m., Alex Rousskov wrote:
>>> Hello,
>>>
>>> The attached trunk patch fixes a rare but nasty problem by removing
>>> a very old hack which shielded Squid from parsing most CONNECT
On 06/19/2015 06:46 PM, Amos Jeffries wrote:
> On 20/06/2015 4:54 a.m., Alex Rousskov wrote:
>> Hello,
>>
>> The attached trunk patch fixes a rare but nasty problem by removing
>> a very old hack which shielded Squid from parsing most CONNECT responses.
>>
>> Currently, Squid blindly forwards c
On 20/06/2015 4:54 a.m., Alex Rousskov wrote:
> Hello,
>
> The attached trunk patch fixes a rare but nasty problem by removing
> a very old hack which shielded Squid from parsing most CONNECT responses.
>
> Currently, Squid blindly forwards cache peer CONNECT responses to
> clients when possi
Hello,
The attached trunk patch fixes a rare but nasty problem by removing
a very old hack which shielded Squid from parsing most CONNECT responses.
Currently, Squid blindly forwards cache peer CONNECT responses to
clients when possible. This may break things if the peer responds with
somethi
