On Wed, 29 Jul 2009 08:37:47 -0500, "Dean Weimer" <dweimer@xxxxxxxxxxxx> wrote: >> -----Original Message----- >> From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] >> Sent: Monday, July 27, 2009 10:01 AM >> To: Martin.Pichlmaier@xxxxxxxxxxxxxxxxxxxxxxxxxxx >> Cc: Squid >> Subject: Re: Antwort: [squid-users] Squid 3.0.STABLE17 > is >> available >> >> Amos Jeffries wrote: >> > Martin.Pichlmaier@xxxxxxxxxxxxxxxxxxxxxxxxxxx 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
