RE: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
On Wed, 29 Jul 2009 08:37:47 -0500, "Dean Weimer"
wrote:
>> -Original Message-
>> From: Amos Jeffries [mailto:squ...@treenet.co.nz]
>> Sent: Monday, July 27, 2009 10:01 AM
>> To: martin.pichlma...@continental-corporation.com
>> Cc: Squid
>> Subject: Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17
> is
>> available
>>
>> Amos Jeffries wrote:
>> > martin.pichlma...@continental-corporation.com wrote:
>> >> Hello all,
>> >>
>> >> I just compiled squid-3.0.STABLE17 and it compiled fine.
>> >> Unfortunately I now get many warning messages in cache.log (still
>> >> testing, not yet in productive environment):
>> >> 2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is
>> >> invalid
>> >> 2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is
>> >> invalid
>> >> 2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is
>> >> invalid
>> >> 2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is
>> >> invalid
>> >> 2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is
>> >> invalid
>> >>
>> >> It seems that nearly every URL I try to access gives that warning
>> >> message,
>> >> for example www.arin.net, www.ripe.net, www.hp.com,
>> >> www.arin.net, even www.squid-cache.org and so on.
>> >> Are nearly all pages in the internet invalid or is the if-query or
>> >> rather the function incorrect?
>> >> The lines that produce the above warning are new in STABLE17...
>> >>
>> >> HttpMsg.cc -- lines 156 to 160:
>> >> if (!sanityCheckStartLine(buf, hdr_len, error)) {
>> >> debugs(58,1, HERE << "first line of HTTP message is
>> invalid");
>> >> // NP: sanityCheck sets *error
>> >> return false;
>> >> }
>> >>
>> >
>> > Oh dear. I missed a bit in the upgrade. Thanks.
>> > This attached patch should quieten it down to only the real errors.
>> >
>> > Amos
>> >
>>
>> Oh foey. forget that patch. It pasted badly.
>>
>> Here is the real one.
>>
>> Amos
>> --
>> Please be using
>>Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
>>Current Beta Squid 3.1.0.12
>
> Amos,
> Was this fixed on the 3.0.STABLE17 that's on the download site?
> Or do I still need to run this patch if I downloaded it today before
> installing it?
Todays snapshot you still have to patch. I don't have time for maintenance
until tomorrow.
Amos
RE: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
> -Original Message-
> From: Amos Jeffries [mailto:squ...@treenet.co.nz]
> Sent: Monday, July 27, 2009 10:01 AM
> To: martin.pichlma...@continental-corporation.com
> Cc: Squid
> Subject: Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17
is
> available
>
> Amos Jeffries wrote:
> > martin.pichlma...@continental-corporation.com wrote:
> >> Hello all,
> >>
> >> I just compiled squid-3.0.STABLE17 and it compiled fine.
> >> Unfortunately I now get many warning messages in cache.log (still
> >> testing, not yet in productive environment):
> >> 2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is
> >> invalid
> >> 2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is
> >> invalid
> >> 2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is
> >> invalid
> >> 2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is
> >> invalid
> >> 2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is
> >> invalid
> >>
> >> It seems that nearly every URL I try to access gives that warning
> >> message,
> >> for example www.arin.net, www.ripe.net, www.hp.com,
> >> www.arin.net, even www.squid-cache.org and so on.
> >> Are nearly all pages in the internet invalid or is the if-query or
> >> rather the function incorrect?
> >> The lines that produce the above warning are new in STABLE17...
> >>
> >> HttpMsg.cc -- lines 156 to 160:
> >> if (!sanityCheckStartLine(buf, hdr_len, error)) {
> >> debugs(58,1, HERE << "first line of HTTP message is
> invalid");
> >> // NP: sanityCheck sets *error
> >> return false;
> >> }
> >>
> >
> > Oh dear. I missed a bit in the upgrade. Thanks.
> > This attached patch should quieten it down to only the real errors.
> >
> > Amos
> >
>
> Oh foey. forget that patch. It pasted badly.
>
> Here is the real one.
>
> Amos
> --
> Please be using
>Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
>Current Beta Squid 3.1.0.12
Amos,
Was this fixed on the 3.0.STABLE17 that's on the download site?
Or do I still need to run this patch if I downloaded it today before
installing it?
Re: [squid-users] Re: Antwort: Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
On Tue, 28 Jul 2009 11:54:29 -0700, George Herbert
wrote:
> Cool. Is there going to be a STABLE17A or something, or do we have to
> hand-patch for now?
The next formally bundled will be STABLE18. However the daily snapshots
serve as intermediate updates on STABLE
(http://www.squid-cache.org/Versions/v3/3.0/).
I just have not yet had time to apply these fixes to the branch yet.
Amos
>
> Thanks!
>
> On Tue, Jul 28, 2009 at 12:41 AM, Amos Jeffries
> wrote:
>> martin.pichlma...@continental-corporation.com wrote:
>>>
>>> Thank you Amos,
>>>
>>> your patch did the trick, it now works smoothly.
>>> I didn't have time to test yesterday, therefore sorry for my late
>>> response.
>>>
>>> Martin
>>>
>>>
>>>
>>>
>>> Amos Jeffries 27.07.2009 17:00
>>>
>>> An
>>> martin.pichlma...@continental-corporation.com
>>> Kopie
>>> Squid
>>> Thema
>>> Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is
available
>>>
>>>
>>>
>>>
>>>
>>>
>>> Amos Jeffries wrote:
>>>>
>>>> martin.pichlma...@continental-corporation.com wrote:
>>>>>
>>>>> Hello all,
>>>>>
>>>>> I just compiled squid-3.0.STABLE17 and it compiled fine.
>>>>> Unfortunately I now get many warning messages in cache.log (still
>>>>> testing, not yet in productive environment):
>>>>> 2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is
>>>>> invalid
>>>>> 2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is
>>>>> invalid
>>>>> 2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is
>>>>> invalid
>>>>> 2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is
>>>>> invalid
>>>>> 2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is
>>>>> invalid
>>>>>
>>>>> It seems that nearly every URL I try to access gives that warning
>>>>> message,
>>>>> for example www.arin.net, www.ripe.net, www.hp.com,
>>>>> www.arin.net, even www.squid-cache.org and so on.
>>>>> Are nearly all pages in the internet invalid or is the if-query or
>>>>> rather the function incorrect?
>>>>> The lines that produce the above warning are new in STABLE17...
>>>>>
>>>>> HttpMsg.cc -- lines 156 to 160:
>>>>>if (!sanityCheckStartLine(buf, hdr_len, error)) {
>>>>>debugs(58,1, HERE << "first line of HTTP message is
>>>>> invalid");
>>>>>// NP: sanityCheck sets *error
>>>>>return false;
>>>>>}
>>>>>
>>>> Oh dear. I missed a bit in the upgrade. Thanks.
>>>> This attached patch should quieten it down to only the real errors.
>>>>
>>>> Amos
>>>>
>>>
>>> Oh foey. forget that patch. It pasted badly.
>>>
>>> Here is the real one.
>>>
>>> Amos
>>
>> Thank you very much for the feedback.
>>
>> If you noticed, the pconn complaint others made earlier slipped into
that
>> patch too. :)
>>
>>
>> Amos
>> --
>> Please be using
>> Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
>> Current Beta Squid 3.1.0.12
>>
Re: [squid-users] Re: Antwort: Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
Cool. Is there going to be a STABLE17A or something, or do we have to
hand-patch for now?
Thanks!
On Tue, Jul 28, 2009 at 12:41 AM, Amos Jeffries wrote:
> martin.pichlma...@continental-corporation.com wrote:
>>
>> Thank you Amos,
>>
>> your patch did the trick, it now works smoothly.
>> I didn't have time to test yesterday, therefore sorry for my late
>> response.
>>
>> Martin
>>
>>
>>
>>
>> Amos Jeffries 27.07.2009 17:00
>>
>> An
>> martin.pichlma...@continental-corporation.com
>> Kopie
>> Squid
>> Thema
>> Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
>>
>>
>>
>>
>>
>>
>> Amos Jeffries wrote:
>>>
>>> martin.pichlma...@continental-corporation.com wrote:
>>>>
>>>> Hello all,
>>>>
>>>> I just compiled squid-3.0.STABLE17 and it compiled fine.
>>>> Unfortunately I now get many warning messages in cache.log (still
>>>> testing, not yet in productive environment):
>>>> 2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is
>>>> invalid
>>>> 2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is
>>>> invalid
>>>> 2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is
>>>> invalid
>>>> 2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is
>>>> invalid
>>>> 2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is
>>>> invalid
>>>>
>>>> It seems that nearly every URL I try to access gives that warning
>>>> message,
>>>> for example www.arin.net, www.ripe.net, www.hp.com,
>>>> www.arin.net, even www.squid-cache.org and so on.
>>>> Are nearly all pages in the internet invalid or is the if-query or
>>>> rather the function incorrect?
>>>> The lines that produce the above warning are new in STABLE17...
>>>>
>>>> HttpMsg.cc -- lines 156 to 160:
>>>> if (!sanityCheckStartLine(buf, hdr_len, error)) {
>>>> debugs(58,1, HERE << "first line of HTTP message is invalid");
>>>> // NP: sanityCheck sets *error
>>>> return false;
>>>> }
>>>>
>>> Oh dear. I missed a bit in the upgrade. Thanks.
>>> This attached patch should quieten it down to only the real errors.
>>>
>>> Amos
>>>
>>
>> Oh foey. forget that patch. It pasted badly.
>>
>> Here is the real one.
>>
>> Amos
>
> Thank you very much for the feedback.
>
> If you noticed, the pconn complaint others made earlier slipped into that
> patch too. :)
>
>
> Amos
> --
> Please be using
> Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
> Current Beta Squid 3.1.0.12
>
--
-george william herbert
george.herb...@gmail.com
[squid-users] Re: Antwort: Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
martin.pichlma...@continental-corporation.com wrote:
Thank you Amos,
your patch did the trick, it now works smoothly.
I didn't have time to test yesterday, therefore sorry for my late
response.
Martin
Amos Jeffries
27.07.2009 17:00
An
martin.pichlma...@continental-corporation.com
Kopie
Squid
Thema
Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
Amos Jeffries wrote:
martin.pichlma...@continental-corporation.com wrote:
Hello all,
I just compiled squid-3.0.STABLE17 and it compiled fine.
Unfortunately I now get many warning messages in cache.log (still
testing, not yet in productive environment):
2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is
invalid
It seems that nearly every URL I try to access gives that warning
message,
for example www.arin.net, www.ripe.net, www.hp.com,
www.arin.net, even www.squid-cache.org and so on.
Are nearly all pages in the internet invalid or is the if-query or
rather the function incorrect?
The lines that produce the above warning are new in STABLE17...
HttpMsg.cc -- lines 156 to 160:
if (!sanityCheckStartLine(buf, hdr_len, error)) {
debugs(58,1, HERE << "first line of HTTP message is invalid");
// NP: sanityCheck sets *error
return false;
}
Oh dear. I missed a bit in the upgrade. Thanks.
This attached patch should quieten it down to only the real errors.
Amos
Oh foey. forget that patch. It pasted badly.
Here is the real one.
Amos
Thank you very much for the feedback.
If you noticed, the pconn complaint others made earlier slipped into
that patch too. :)
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
Current Beta Squid 3.1.0.12
[squid-users] Antwort: Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
Thank you Amos,
your patch did the trick, it now works smoothly.
I didn't have time to test yesterday, therefore sorry for my late
response.
Martin
Amos Jeffries
27.07.2009 17:00
An
martin.pichlma...@continental-corporation.com
Kopie
Squid
Thema
Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
Amos Jeffries wrote:
> martin.pichlma...@continental-corporation.com wrote:
>> Hello all,
>>
>> I just compiled squid-3.0.STABLE17 and it compiled fine.
>> Unfortunately I now get many warning messages in cache.log (still
>> testing, not yet in productive environment):
>> 2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is
>> invalid
>> 2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is
>> invalid
>> 2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is
>> invalid
>> 2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is
>> invalid
>> 2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is
>> invalid
>>
>> It seems that nearly every URL I try to access gives that warning
>> message,
>> for example www.arin.net, www.ripe.net, www.hp.com,
>> www.arin.net, even www.squid-cache.org and so on.
>> Are nearly all pages in the internet invalid or is the if-query or
>> rather the function incorrect?
>> The lines that produce the above warning are new in STABLE17...
>>
>> HttpMsg.cc -- lines 156 to 160:
>> if (!sanityCheckStartLine(buf, hdr_len, error)) {
>> debugs(58,1, HERE << "first line of HTTP message is invalid");
>> // NP: sanityCheck sets *error
>> return false;
>> }
>>
>
> Oh dear. I missed a bit in the upgrade. Thanks.
> This attached patch should quieten it down to only the real errors.
>
> Amos
>
Oh foey. forget that patch. It pasted badly.
Here is the real one.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
Current Beta Squid 3.1.0.12
=== modified file 'src/HttpMsg.cc'
--- src/HttpMsg.cc 2009-07-26 11:33:16 +
+++ src/HttpMsg.cc 2009-07-27 13:55:53 +
@@ -154,8 +154,7 @@
// sanity check the start line to see if this is in fact an HTTP
message
if (!sanityCheckStartLine(buf, hdr_len, error)) {
-debugs(58,1, HERE << "first line of HTTP message is invalid");
-// NP: sanityCheck sets *error
+// NP: sanityCheck sets *error and sends debug warnings.
return false;
}
=== modified file 'src/HttpReply.cc'
--- src/HttpReply.cc 2009-07-26 12:04:45 +
+++ src/HttpReply.cc 2009-07-27 14:59:48 +
@@ -446,8 +446,10 @@
// content is long enough to possibly hold a reply
// 4 being magic size of a 3-digit number plus space delimiter
if ( buf->contentSize() < (protoPrefix.size() + 4) ) {
-if (hdr_len > 0)
+if (hdr_len > 0) {
+debugs(58, 3, "HttpReply::sanityCheckStartLine: Too small
reply header (" << hdr_len << " bytes)");
*error = HTTP_INVALID_HEADER;
+}
return false;
}
=== modified file 'src/HttpRequest.cc'
--- src/HttpRequest.cc 2009-07-26 11:33:16 +
+++ src/HttpRequest.cc 2009-07-27 14:59:29 +
@@ -156,6 +156,7 @@
if ( buf->contentSize() < 2 ) {
// this is ony a real error if the headers apparently complete.
if (hdr_len > 0) {
+debugs(58, 3, "HttpRequest::sanityCheckStartLine: Too small
request header (" << hdr_len << " bytes)");
*error = HTTP_INVALID_HEADER;
}
return false;
=== modified file 'src/pconn.cc'
--- src/pconn.cc 2009-02-19 02:17:28 +
+++ src/pconn.cc 2009-07-27 08:04:11 +
@@ -188,7 +188,7 @@
else
snprintf(buf, SQUIDHOSTNAMELEN * 3 + 10, "%s:%d", host, (int)
port);
-debugs(48,6,"PconnPool::key(" << host << "," << port << "," << domain
<< "," << inet_ntoa(*client_address) << "is {" << buf << "}" );
+debugs(48,6,"PconnPool::key(" << (host?host:"") << "," << port << ","
<< (domain?domain:"") << "," <<
(client_address?inet_ntoa(*client_address):"") << "is {" << buf << "}" );
return buf;
}
Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
Amos Jeffries wrote:
martin.pichlma...@continental-corporation.com wrote:
Hello all,
I just compiled squid-3.0.STABLE17 and it compiled fine.
Unfortunately I now get many warning messages in cache.log (still
testing, not yet in productive environment):
2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is
invalid
2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is
invalid
It seems that nearly every URL I try to access gives that warning
message,
for example www.arin.net, www.ripe.net, www.hp.com,
www.arin.net, even www.squid-cache.org and so on.
Are nearly all pages in the internet invalid or is the if-query or
rather the function incorrect?
The lines that produce the above warning are new in STABLE17...
HttpMsg.cc -- lines 156 to 160:
if (!sanityCheckStartLine(buf, hdr_len, error)) {
debugs(58,1, HERE << "first line of HTTP message is invalid");
// NP: sanityCheck sets *error
return false;
}
Oh dear. I missed a bit in the upgrade. Thanks.
This attached patch should quieten it down to only the real errors.
Amos
Oh foey. forget that patch. It pasted badly.
Here is the real one.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
Current Beta Squid 3.1.0.12
=== modified file 'src/HttpMsg.cc'
--- src/HttpMsg.cc 2009-07-26 11:33:16 +
+++ src/HttpMsg.cc 2009-07-27 13:55:53 +
@@ -154,8 +154,7 @@
// sanity check the start line to see if this is in fact an HTTP message
if (!sanityCheckStartLine(buf, hdr_len, error)) {
-debugs(58,1, HERE << "first line of HTTP message is invalid");
-// NP: sanityCheck sets *error
+// NP: sanityCheck sets *error and sends debug warnings.
return false;
}
=== modified file 'src/HttpReply.cc'
--- src/HttpReply.cc 2009-07-26 12:04:45 +
+++ src/HttpReply.cc 2009-07-27 14:59:48 +
@@ -446,8 +446,10 @@
// content is long enough to possibly hold a reply
// 4 being magic size of a 3-digit number plus space delimiter
if ( buf->contentSize() < (protoPrefix.size() + 4) ) {
-if (hdr_len > 0)
+if (hdr_len > 0) {
+debugs(58, 3, "HttpReply::sanityCheckStartLine: Too small reply header (" << hdr_len << " bytes)");
*error = HTTP_INVALID_HEADER;
+}
return false;
}
=== modified file 'src/HttpRequest.cc'
--- src/HttpRequest.cc 2009-07-26 11:33:16 +
+++ src/HttpRequest.cc 2009-07-27 14:59:29 +
@@ -156,6 +156,7 @@
if ( buf->contentSize() < 2 ) {
// this is ony a real error if the headers apparently complete.
if (hdr_len > 0) {
+debugs(58, 3, "HttpRequest::sanityCheckStartLine: Too small request header (" << hdr_len << " bytes)");
*error = HTTP_INVALID_HEADER;
}
return false;
=== modified file 'src/pconn.cc'
--- src/pconn.cc 2009-02-19 02:17:28 +
+++ src/pconn.cc 2009-07-27 08:04:11 +
@@ -188,7 +188,7 @@
else
snprintf(buf, SQUIDHOSTNAMELEN * 3 + 10, "%s:%d", host, (int) port);
-debugs(48,6,"PconnPool::key(" << host << "," << port << "," << domain << "," << inet_ntoa(*client_address) << "is {" << buf << "}" );
+debugs(48,6,"PconnPool::key(" << (host?host:"") << "," << port << "," << (domain?domain:"") << "," << (client_address?inet_ntoa(*client_address):"") << "is {" << buf << "}" );
return buf;
}
Re: [squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
martin.pichlma...@continental-corporation.com wrote:
Hello all,
I just compiled squid-3.0.STABLE17 and it compiled fine.
Unfortunately I now get many warning messages in cache.log (still testing,
not yet in productive environment):
2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is invalid
It seems that nearly every URL I try to access gives that warning message,
for example www.arin.net, www.ripe.net, www.hp.com,
www.arin.net, even www.squid-cache.org and so on.
Are nearly all pages in the internet invalid or is the if-query or rather
the function incorrect?
The lines that produce the above warning are new in STABLE17...
HttpMsg.cc -- lines 156 to 160:
if (!sanityCheckStartLine(buf, hdr_len, error)) {
debugs(58,1, HERE << "first line of HTTP message is invalid");
// NP: sanityCheck sets *error
return false;
}
Oh dear. I missed a bit in the upgrade. Thanks.
This attached patch should quieten it down to only the real errors.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16
Current Beta Squid 3.1.0.10 or 3.1.0.11
=== modified file 'src/HttpMsg.cc'
--- src/HttpMsg.cc 2009-07-26 11:33:16 +
+++ src/HttpMsg.cc 2009-07-27 13:55:53 +
@@ -154,8 +154,7 @@
// sanity check the start line to see if this is in fact an HTTP message
if (!sanityCheckStartLine(buf, hdr_len, error)) {
-debugs(58,1, HERE << "first line of HTTP message is invalid");
-// NP: sanityCheck sets *error
+// NP: sanityCheck sets *error and sends debug warnings.
return false;
}
=== modified file 'src/HttpReply.cc'
--- src/HttpReply.cc 2009-07-26 12:04:45 +
+++ src/HttpReply.cc 2009-07-27 14:01:49 +
@@ -446,8 +446,10 @@
// content is long enough to possibly hold a reply
// 4 being magic size of a 3-digit number plus space delimiter
if ( buf->contentSize() < (protoPrefix.size() + 4) ) {
-if (hdr_len > 0)
+if (hdr_len > 0) {
+debugs(58, 3, "HttpReply::sanityCheckStartLine: Too large reply header (" << hdr_len << " > " << Config.maxReplyHeaderSize <<")");
*error = HTTP_INVALID_HEADER;
+}
return false;
}
=== modified file 'src/HttpRequest.cc'
--- src/HttpRequest.cc 2009-07-26 11:33:16 +
+++ src/HttpRequest.cc 2009-07-27 14:02:36 +
@@ -156,6 +156,7 @@
if ( buf->contentSize() < 2 ) {
// this is ony a real error if the headers apparently complete.
if (hdr_len > 0) {
+debugs(58, 3, "HttpRequest::sanityCheckStartLine: debugs(58, 1, "HttpMsg::parse: Too large reply header (" << hdr_len << " > " << Config.maxReplyHeaderSize <<")");
*error = HTTP_INVALID_HEADER;
}
return false;
=== modified file 'src/pconn.cc'
--- src/pconn.cc 2009-02-19 02:17:28 +
+++ src/pconn.cc 2009-07-27 08:04:11 +
@@ -188,7 +188,7 @@
else
snprintf(buf, SQUIDHOSTNAMELEN * 3 + 10, "%s:%d", host, (int) port);
-debugs(48,6,"PconnPool::key(" << host << "," << port << "," << domain << "," << inet_ntoa(*client_address) << "is {" << buf << "}" );
+debugs(48,6,"PconnPool::key(" << (host?host:"") << "," << port << "," << (domain?domain:"") << "," << (client_address?inet_ntoa(*client_address):"") << "is {" << buf << "}" );
return buf;
}
[squid-users] Antwort: [squid-users] Squid 3.0.STABLE17 is available
Hello all,
I just compiled squid-3.0.STABLE17 and it compiled fine.
Unfortunately I now get many warning messages in cache.log (still testing,
not yet in productive environment):
2009/07/27 15:11:26| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:28| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:37| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:38| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:40| HttpMsg.cc(157) first line of HTTP message is invalid
2009/07/27 15:11:41| HttpMsg.cc(157) first line of HTTP message is invalid
It seems that nearly every URL I try to access gives that warning message,
for example www.arin.net, www.ripe.net, www.hp.com,
www.arin.net, even www.squid-cache.org and so on.
Are nearly all pages in the internet invalid or is the if-query or rather
the function incorrect?
The lines that produce the above warning are new in STABLE17...
HttpMsg.cc -- lines 156 to 160:
if (!sanityCheckStartLine(buf, hdr_len, error)) {
debugs(58,1, HERE << "first line of HTTP message is invalid");
// NP: sanityCheck sets *error
return false;
}
Maybe it has something to do with my configuration options. I complied
squid with:
# squid -v
Squid Cache: Version 3.0.STABLE17
configure options: '--prefix=/appl' '--localstate=/var'
'--with-filedescriptors=16384' '--enable-storeio=ufs,null'
'--enable-auth=ntlm,basic' '--enable-external-acl-helpers=wbinfo_group'
'--enable-icap-client'
# uname -a
Linux proxy 2.6.18-92.1.10.0.1.el5 #1 SMP Mon Aug 4 17:11:38 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux
#
I could shut it out with "debug_options ALL,1 58,0" but don't know which
other important messages I may miss.
Best regards,
Martin
Amos Jeffries
27.07.2009 13:00
An
squid-annou...@squid-cache.org, Squid
Kopie
Thema
[squid-users] Squid 3.0.STABLE17 is available
The Squid HTTP Proxy team is pleased to announce the
availability of the Squid-3.0.STABLE17 release!
This release is primarily a Security Update release.
All users of Squid-3.0 are urgently advised to move up to this release.
The major changes are for advisory SQUID-2009:2. This is for multiple
vulnerabilities in both request and response processing. The cause is
the same, but there are many variations of possible attack.
http://www.squid-cache.org/Advisories/SQUID-2009_2.txt
There are also a number of smaller fixes in this release with potential
towards security problems. These are much harder trigger within Squid.
The helper issues are primarily of concern when used by other systems
than Squid.
- Bug 2710: squid_kerb_auth non-terminated string
- Bug 2674: Remove limit on HTTP headers read.
- Bug 2659: String length overflows on append, leading to segfaults
- Bug 2620: Invalid HTTP response codes causes segfault
- Bug 2080: wbinfo_group.pl - false positive under certain conditions
And a few more regular bugs:
- Bug 2680 regression: Crash after rotate with no helpers running
- Bug 2679: strsep and strtoll detection failure
- Bug 1087: ESI processor not quoting attributes correctly.
- Fix: issue with AUFS/UFS/DiskD writing objects to disk cache
Please refer to the release notes at
http://www.squid-cache.org/Versions/v3/3.0/RELEASENOTES.html
if and when you are ready to make the switch to Squid-3.
This new release can be downloaded from our HTTP or FTP servers
http://www.squid-cache.org/Versions/v3/3.0/
ftp://ftp.squid-cache.org/pub/squid-3/STABLE/
or the mirrors. For a list of mirror sites see
http://www.squid-cache.org/Download/http-mirrors.dyn
http://www.squid-cache.org/Download/mirrors.dyn
If you encounter any issues with this release please file a bug report.
http://bugs.squid-cache.org/
Amos Jeffries
