On 13/05/2014 5:11 a.m., Tom Holder wrote:
I haven't investigated exactly, however, I'm guessing it's simply not
trying to mimic the original SSL and is just generating one that is
'good-enough'. For my purposes, good enough is erm, good enough.
Exactly so.
Amos
Tom
On Mon, May 12,
Hi!
I tried to compile squid-3.4.5-20140508-r13134.
uname -a
Linux hmsmbsrv 2.6.22.19-0.2-default #1 SMP 2008-12-18 10:17:03 +0100
x86_64 x86_64 x86_64 GNU/Linux
cat /etc/SuSE-release
openSUSE 10.3 (X86-64)
VERSION = 10.3
./configure '--prefix=/usr' '--sysconfdir=/etc/squid'
On Mon, Feb 24, 2014 at 11:42 PM, Alex Rousskov
rouss...@measurement-factory.com wrote:
This assertion is being tracked as misnamed bug 3279 (at least). Posting
a backtrace from the assertion there may help. If you do that, please
indicate what cache_dir store module(s) you are using.
I'm
I'm getting these too in 3.3.11 with aufs on FreeBSD. So I use diskd
instead of aufs.
Regards
Simon
δΊ 14-5-14 0:06, csn233 ει:
On Mon, Feb 24, 2014 at 11:42 PM, Alex Rousskov
rouss...@measurement-factory.com wrote:
This assertion is being tracked as misnamed bug 3279 (at least). Posting
a
On Wed, May 14, 2014 at 12:14 AM, k simon chio1...@gmail.com wrote:
I'm getting these too in 3.3.11 with aufs on FreeBSD. So I use diskd instead
of aufs.
Are you saying with diskd, this error does not occur?
Hi guys,
I am trying to set up an https reverse proxy to cache and proxy a data
feed from a 3rd party.
At the moment, as a POC inside a VirtualBox VM, I am simply trying to
reverse proxy https://localhost to fetch https://www.google.com (or
any other https site).
Unfortunately, I consistently
On 14/05/2014 4:34 a.m., Nico Snyman wrote:
Hi guys,
I am trying to set up an https reverse proxy to cache and proxy a data
feed from a 3rd party.
At the moment, as a POC inside a VirtualBox VM, I am simply trying to
reverse proxy https://localhost to fetch https://www.google.com (or
any
On 05/13/2014 10:06 AM, csn233 wrote:
On Mon, Feb 24, 2014 at 11:42 PM, Alex Rousskov
rouss...@measurement-factory.com wrote:
This assertion is being tracked as misnamed bug 3279 (at least). Posting
a backtrace from the assertion there may help. If you do that, please
indicate what