Hello Gurus,
I am sorry to send this question, but my search could not generate anything
useful.
Server HP DL380 with 1GB RAM
72GB ULTRA FAST SCSI
RHES -3
# uname -a
Linux BM 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT 2004 i686 i686 i386
Hello Gurus,
I am sorry to send this question, but my search could not
generate anything
useful.
Server HP DL380 with 1GB RAM
72GB ULTRA FAST SCSI
RHES -3
# uname -a
Linux BM 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT
What should I look for in logs?
Regards,
Rikunj Patel
Systems Administrator --Raha.com
- Original Message -
From: Elsen Marc [EMAIL PROTECTED]
To: Rikunj [EMAIL PROTECTED]; squid-users@squid-cache.org
Sent: Tuesday, April 12, 2005 6:15 PM
Subject: RE: [squid-users] Request header
What should I look for in logs?
...
Difficult to tell.
You may want to set :
log_mime_hdrs on
in order to identify 'large' request headers send
to squid.
M.
Hi
I'm facing this same problem of Header size from many customers, but most of
them use PPPOE . For some of them wccp does not work, so they are asked to
configure the proxy in their browser. Does this cause them from being able
to browse( because many i had to bypass from wccp ).
Have been
On 13.09 13:21, Henrik Nordstrom wrote:
On Mon, 13 Sep 2004, Eswari sharma wrote:
I am facing the same problem .I am using squid-2.5STABLE3 and wccp v1, In
my
squid.conf request_header_max_size is disable.
request_header_max_size can not be disabled, only increased.
Is there any way
On Tue, 14 Sep 2004, Matus UHLAR - fantomas wrote:
maybe someone using GET to send data to server...
Maybe, or maybe something is trying to use GET to hack buffer overflows on
Internet servers by sending excessive amounts of data un the URL or
certain request headers were there is known
Ahmed wrote :
I am getting a lot of these messages in my cache.log
2004/04/23 02:21:02| Request header is too large (10494 bytes)
2004/04/23 02:21:02| Config 'request_header_max_size'= 10240 bytes.
2004/04/23 02:21:30| Request header is too large (11680 bytes)
2004/04/23 02:21:30|
On Mon, 13 Sep 2004, Eswari sharma wrote:
I am facing the same problem .I am using squid-2.5STABLE3 and wccp v1, In my
squid.conf request_header_max_size is disable.
request_header_max_size can not be disabled, only increased.
Is there any way to stop these messages in cache.log ? As you said I
Hello All
I am getting a lot of these messages in my cache.log
2004/04/23 02:21:02| Request header is too large (10494 bytes)
2004/04/23 02:21:02| Config 'request_header_max_size'= 10240 bytes.
2004/04/23 02:21:30| Request header is too large (11680 bytes)
2004/04/23 02:21:30| Config
Hello All
I am getting a lot of these messages in my cache.log
2004/04/23 02:21:02| Request header is too large (10494 bytes)
2004/04/23 02:21:02| Config 'request_header_max_size'= 10240 bytes.
2004/04/23 02:21:30| Request header is too large (11680 bytes)
2004/04/23 02:21:30|
We have two squids,both are 2.5S2.
We are getting this header is too large error all the time,what this
means? it started suddenly with out any config changes...
***cache.log
2003/09/05 14:15:42| Request header is too large (32767 bytes)
2003/09/05 14:15:42| Config 'request_header_max_size'=
We are getting this header is too large error all
the time,what this means?
The cache.log entries tell you all you need to know. It means that a
client sent a request with a header that was too large for your
configured limit. The error message tells you how large the header was
and what the
On Friday 05 September 2003 14.31, Adam Aube wrote:
Using the timestamp, you can likely correlate this with the
access.log entry which will tell you which client was making the
request so you can find out what the client was doing that
triggered this.
And it should be noted that a request
14 matches
Mail list logo
