On Mon, 11 Apr 2005 22:22:16 +0200 (CEST)
Henrik Nordstrom [EMAIL PROTECTED] wrote:
On Mon, 11 Apr 2005, Evgeny Kotsuba wrote:
Is helperHandleRead() called in situation when squid just started
but there
is no one client connection ?
helperHandleRead is always pending for read from the
On Tue, 12 Apr 2005, Steven Wilton wrote:
My thoughts were that if the numbers for %CPU in system and user were
similar, then a more efficient filesystem would arrange the data on disk
in such a way that the disk spends less time performing the operations.
Partly true, but the problem is that the
On Tue, 12 Apr 2005, Evgeny Kotsuba wrote:
But what in case if there is no activity on the helper?
There is activity on the helper when Squid asks it to shut down by closing
the write fd squid-helper.
If we have N redirectors, then there is the chances than some of them
will never called ,
On Tue, 12 Apr 2005, Evgeny Kotsuba wrote:
Has this [strange] message in log any reasonable information ?
WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
squid 2.5.x
This is commonly seen from broken web servers sending two status lines,
presumably caused by a bad CGI or similar
On Mon, 2005/04/11 (MDT), [EMAIL PROTECTED] wrote:
We currently get arount 70 reqs/sec using 25% CPU (5 minute average for
both values) on this hardware. I'm confident that I'll get a pretty
high number of requests/second through these proxies becase of the epoll
patch.
Polygraph using
On Tue, 12 Apr 2005 12:04:54 +0200 (CEST)
Henrik Nordstrom [EMAIL PROTECTED] wrote:
On Tue, 12 Apr 2005, Evgeny Kotsuba wrote:
Has this [strange] message in log any reasonable information ?
WARNING: unparseable HTTP header field {HTTP/1.0 200 OK}
squid 2.5.x
This is commonly seen from broken
On Wed, 13 Apr 2005, Evgeny Kotsuba wrote:
Well, but there is no any key what server and what is bad in {HTTP/1.0 200
OK} in warning message
Example reply headers where this message is seen:
HTTP/1.1 200 OK
Server: sometthing
HTTP/1.0 200 OK
Content-type: text/html
other headers...
I
