-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi gents,
I observe assertion. Time to time, with irregular interval and witout
visible reasons:
2015/01/06 15:52:10 kid1| storeLateRelease: released 0 objects
2015/01/06 15:52:11 kid1| assertion failed: comm.cc:178:
"fd_table[conn->fd].halfClosedR
On 06/01/15 05:28, Eliezer Croitoru wrote:
> In 3.5 there will be present a new feature which called peek and
> splice that can give an interface to squid and the admin which will
> allow the admin to know couple things about the connection from squid
> and specifically first the client TLS request
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi gents,
old good bug returns.
When build with Solaris Studio, I've got this error:
libtool: compile: /bin/CC -DHAVE_CONFIG_H -I../.. -I../../include
-I../../lib -I../../src -I../../include -I/usr/include/gssapi
-I/usr/include/kerberosv5 -I../..
On 05.01.15 18:15, Amos Jeffries wrote:
Can you try making the constructor at the top of src/HelperReply.cc
look like this and see if it resolves the problem?
HelperReply::HelperReply(char *buf, size_t len) :
result(HelperReply::Unknown),
notes(),
whichServer(NULL)
{
Hi,
Since yesterday, my Squid cache.log grow very fast, about 250Mb per hour. Lot
of messages like this one:
2015/01/06 13:16:31| WARNING: unparseable HTTP header field {24eb927c;
put_2588=48b1dcc8-a78f-4800-9595-62f724eb927c;
put_2261=48b1dcc8-a78f-4800-9595-62f724eb927c;
put_2616=48b1dcc8-a
On 05.01.15 20:11, Eliezer Croitoru wrote:
Did you had the chance to take look at bug 3997:
http://bugs.squid-cache.org/show_bug.cgi?id=3997
This could quite likely be the same issue. See my other post this
morning for details, but I've pretty much tracked this down to the
Negotiate tokens
On 06.01.15 12:15, Steve Hill wrote:
Alternatively, A->absorb(B) could be altered to remove any notes from A
that have the same keys as B's notes, before using appendNewOnly() to
merge them?
I've implemented this for now in the attached patch and am currently
testing it. Initial results sugg
Hi together,
I'm having trouble figuring a way to configure a `squid` 3.4.10 instance
running in a Debian 7 chroot as a transparent caching proxy because I
only find configuration examples involving `iptables` which on the one
hand is very useful because it allows setups which work independently of
