-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The problem is always with the DNA. The main question - by whom;)
21.05.16 0:41, Rob Worsnop пишет:
> Quick update: The problem isn't with Squid.
>
> When MWG decides it wants to send an early response, it seems it also
> decides to send garbage
Quick update: The problem isn't with Squid.
When MWG decides it wants to send an early response, it seems it also
decides to send garbage data after a few KB of valid data. Squid
notices that MWG is trying to send a chunk bigger than advertised and
promptly closes the connection.
On Wed, May 18,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Amos, a paradoxical situation. Changes accumulate and accumulate, and no
new releases at least two weeks.
And these changes appear in the subspace - in the source of their past
is definitely not. So conceived?
20.05.16 21:31, Amos Jeffries пишет:
>
20 мая 2016 г. 18:31 пользователь "Amos Jeffries"
написал:
>
> On 21/05/2016 2:53 a.m., Pavel Timofeev wrote:
> > 20 мая 2016 г. 17:44 пользователь "Amos Jeffries" написал:
> >>
> >> On 21/05/2016 2:28 a.m., Pavel Timofeev wrote:
> >>>
> >>> Hi, Amos!
> >>> Thank you! Should we create a bug report
On 21/05/2016 2:53 a.m., Pavel Timofeev wrote:
> 20 мая 2016 г. 17:44 пользователь "Amos Jeffries" написал:
>>
>> On 21/05/2016 2:28 a.m., Pavel Timofeev wrote:
>>>
>>> Hi, Amos!
>>> Thank you! Should we create a bug report to track it?
>>>
>>
>> No need, I think.
>
> I just wanted to look at some
20 мая 2016 г. 17:44 пользователь "Amos Jeffries"
написал:
>
> On 21/05/2016 2:28 a.m., Pavel Timofeev wrote:
> >
> > Hi, Amos!
> > Thank you! Should we create a bug report to track it?
> >
>
> No need, I think.
I just wanted to look at something and understand that it's done and it's
time to tes
Hello,
I'd like to disable some ciphersuites when connecting with web servers;
when I go there: https://cc.dcsec.uni-hannover.de/
I'm shown this (only the column with ciphersuite names):
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-SHA384
ECDHE-ECDSA-AES256-SHA384
On 21/05/2016 2:28 a.m., Pavel Timofeev wrote:
>
> Hi, Amos!
> Thank you! Should we create a bug report to track it?
>
No need, I think.
Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-us
2016-05-20 17:06 GMT+03:00 Amos Jeffries :
> On 13/05/2016 1:33 a.m., Spil Oss wrote:
>>> Hi!
>>> When we worked on squid port on FreeBSD one of the FreeBSD user
>>> (Bernard Spil) noticed:
>>>
>>> When working on this, I ran into another issue. Perhaps maintainer can
>>> fix that with upstream. I'
On 13/05/2016 1:33 a.m., Spil Oss wrote:
>> Hi!
>> When we worked on squid port on FreeBSD one of the FreeBSD user
>> (Bernard Spil) noticed:
>>
>> When working on this, I ran into another issue. Perhaps maintainer can
>> fix that with upstream. I've now added LIBOPENSSL_LIBS="-lcrypto
>> -lssl" be
On 17/05/2016 6:27 a.m., Eugene M. Zheganin wrote:
> Hi.
>
I dont see any mention of the Squid version. Which one are you having
this issue in?
> I'm using squid for a long time, I'm using it to authenticate/authorize
> users accessing the Internet with LDAP in a Windows corporate
> enviromnent
I'd seen this licensing issue mentioned briefly before, but now I
actually understand what's going on. Thanks for explaining it in detail.
Good to know there's 2 paths moving along to solve the distro problem. I
feel more confident in moving forward with my little project now that I
know it's
12 matches
Mail list logo
