On 2016-11-26 23:42, Ralf Hildebrandt wrote:
* piequiex :
> In cache.log I have found "assertion failed: support.cc:1781: "0""
> Squid Cache: Version 3.5.22
After rebuild:
assertion failed: Read.cc:69: "fd_table[conn->fd].halfClosedReader !=
NULL"
http://lists.squid-cache.org/pipermail/squid-
* piequiex :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> > In cache.log I have found "assertion failed: support.cc:1781: "0""
> > Squid Cache: Version 3.5.22
> After rebuild:
> assertion failed: Read.cc:69: "fd_table[conn->fd].halfClosedReader != NULL"
http://lists.squid-cache.org/piper
On 2016-11-26 22:28, piequiex wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In cache.log I have found "assertion failed: support.cc:1781: "0""
Squid Cache: Version 3.5.22
AIUI, your Squid binary was build against buggy openssl library (1.0.1d
or 1.0.1e). How did you get the binary?
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> In cache.log I have found "assertion failed: support.cc:1781: "0""
> Squid Cache: Version 3.5.22
After rebuild:
assertion failed: Read.cc:69: "fd_table[conn->fd].halfClosedReader != NULL"
- --
0x16E684E1A170D8A3
~~~
This PGP signature only certifi
Thanks for the explanation. We are on not on 3.2 (or greater) yet and
it doesn't appear concurrency is supported, so it looks like a single
threaded redirector for a little while longer.
On Sat, Nov 26, 2016, at 01:44 AM, Amos Jeffries wrote:
> On 26/11/2016 8:54 a.m., cred...@eml.cc wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In cache.log I have found "assertion failed: support.cc:1781: "0""
Squid Cache: Version 3.5.22
- --
0x16E684E1A170D8A3
~~~
This PGP signature only certifies the sender and date of the message.
It implies no approval from the administrators of nym.mi
On 26/11/2016 8:54 a.m., cred...@eml.cc wrote:
> Using the first example in the link that was shared
> (http://wiki.squid-cache.org/Features/Redirectors), I was able to get it
> to work after seeing what was being sent to the redirector script. In
> my case the URL was at $X[0] and I had to remove
