On Wed, Dec 01, 2010 at 11:40:52AM +, Graham Keeling wrote:
Hello,
I am convinced that this is a serious bug, so I have entered a proper bug
report.
It is bug 3113:
http://bugs.squid-cache.org/show_bug.cgi?id=3113
I have created a simple patch that seems to fix the problem for me
Hello,
I am convinced that this is a serious bug, so I have entered a proper bug
report.
It is bug 3113:
http://bugs.squid-cache.org/show_bug.cgi?id=3113
On Tue, Nov 30, 2010 at 09:46:47PM +1300, Amos Jeffries wrote:
On 30/11/10 21:23, Oguz Yilmaz wrote:
On Tue, Nov 30, 2010 at 10:05 AM, Amos Jeffriessqu...@treenet.co.nz wrote:
On 30/11/10 04:04, Oguz Yilmaz wrote:
Graham,
This is the best explanation I have seen about ongoing upload
On Tue, Nov 30, 2010 at 11:31:45AM +, Graham Keeling wrote:
On Tue, Nov 30, 2010 at 09:46:47PM +1300, Amos Jeffries wrote:
On 30/11/10 21:23, Oguz Yilmaz wrote:
On Tue, Nov 30, 2010 at 10:05 AM, Amos Jeffriessqu...@treenet.co.nz
wrote:
On 30/11/10 04:04, Oguz Yilmaz wrote
On Thu, Nov 25, 2010 at 04:36:49PM +, Graham Keeling wrote:
Hello,
I have upgraded to squid-3.1 recently, and found a change of behaviour.
I have been using dansguardian in front of squid.
It appears to be because squid now buffers uploaded POST data slightly
differently.
In versions
Hello,
I have upgraded to squid-3.1 recently, and found a change of behaviour.
I have been using dansguardian in front of squid.
It appears to be because squid now buffers uploaded POST data slightly
differently.
In versions 3.1, it would take some data, send it through to the website,
and then
On Tue, Mar 16, 2010 at 09:46:44PM +, Amos Jeffries wrote:
On Tue, 16 Mar 2010 14:06:59 +, Graham Keeling gra...@equiinet.com
wrote:
Hello,
In older versions of squid, I was able to block or allow specific
arbitrary
request headers. For example:
header_access X
Hello,
In older versions of squid, I was able to block or allow specific arbitrary
request headers. For example:
header_access X-SomeRandomHeaderA allow all
header_access X-SomeRandomHeaderB deny all
In squid-3.1 (and 3.0, I think), the equivalent of header_access for request
headers is now
Hello,
I am trying to upgrade my squid from 2.5 to 3.1.
I have got all my old configuration working on 3.1, except...
I am coming across a problem with WCCPv1.
172.16.13.56 is the address of the squid box.
172.16.13.2 is the address of the cisco router.
I have wccp_router=172.16.13.2 in my
On Fri, Jan 29, 2010 at 11:35:00AM +, Graham Keeling wrote:
Hello,
I am trying to upgrade my squid from 2.5 to 3.1.
I have got all my old configuration working on 3.1, except...
I am coming across a problem with WCCPv1.
172.16.13.56 is the address of the squid box.
172.16.13.2
On Fri, Jan 29, 2010 at 03:59:29PM +, Graham Keeling wrote:
On Fri, Jan 29, 2010 at 11:35:00AM +, Graham Keeling wrote:
Hello,
I am trying to upgrade my squid from 2.5 to 3.1.
I have got all my old configuration working on 3.1, except...
I am coming across a problem with WCCPv1
11 matches
Mail list logo
