Something seems to have gone wrong with error page generation in the
3.1.0.16 tarball. errors/ca/ERR_CACHE_ACCESS_DENIED is empty.
Regards
Henrik
sön 2010-02-07 klockan 15:43 +1300 skrev Amos Jeffries:
Yes, there was for a few hours a bundle that did not build.
The signature got as far as HTTP east/west before I erased everything
and started again.
And I picked up the first when building 3.1.0.16 for Fedora, which
caused some major
Hello,
I started a thread over here with the initial problems that I had with
squid-3.1.0.15:
http://www.mail-archive.com/squid-us...@squid-cache.org/msg69906.html
That thread ends with me setting the router port in src/wccp.cc and I say
that WCCPv1 was working for me.
Well, I was mistaken, as
Hi,
I'm working on a project aimed at developing dynamic/intelligent
bandwidth controlling
techniques as a part of my Masters work.
I'm developing a system that intelligently decides the maximum amount
of bandwidth
allowed for a given connection, I would like to extend Squid delay
pools as a POC.
On Sun, 2010-02-07 at 00:52 +1300, Amos Jeffries wrote:
According to the W3C documentation the Surrogate/1.0 capabilities and
the Surrogate-Control: header are distinct from the ESI capabilities.
This patch makes Squid always advertise and perform the Surrogate/1.0
capabilities for
