[squid-users] Assertion error on unparseable header

Yesterday I upgraded a proxy server from Mandrake 10.0 to Mandrake 10.1,
which upgraded Squid from 2.5 STABLE4 to 2.5 STABLE6 (with later
security patches folded in by Mandrake). Now I'm seeing errors such as
this every few hours:

2005/03/16 09:22:09| ctx: enter level 0:
'http://www.tescohs.co.uk/images/elec/thumb/small/39W705.jpg'
2005/03/16 09:22:09| WARNING: unparseable HTTP header field near { The
file does not exist or is read-protected.
Server: Domino-Go-Webserver/4.6.2.50
Date: Wed, 16 Mar 2005 09:35:54 GMT
Connection: close
Accept-Ranges: bytes
Content-Type: text/html; charset=ISO8859-1
Content-Length: 346
Last-Modified: Wed, 16 Mar 2005 09:35:54 GMT
Expires: Wed, 16 Mar 2005 09:35:54 GMT
Pragma: no-cache
Cache-Control: no-cache
}
2005/03/16 09:22:09| ctx: exit level 0
2005/03/16 09:22:09| assertion failed: MemBuf.c:188: "mb->buf &&
mb->max_capacity && mb->capacity"
2005/03/16 09:22:12| Starting Squid Cache version 2.5.STABLE6 for
i586-mandrake-linux-gnu...

I haven't seen this exact error in Bugzilla or on the mailing list,
though I see later Squid versions have patches for broken HTTP.

The next Mandrake release (10.2 due next Month) seems to stick with
Squid 2.5 STABLE6. To fix this problem should I use the latest Squid
version built from source?

-- 
Dave
The information contained in this message (and any attachments) may 
be confidential and is intended for the sole use of the named addressee. 
Access, copying, alteration or re-use of the e-mail by anyone other 
than the intended recipient is unauthorised. If you are not the intended 
recipient please advise the sender immediately by returning the e-mail 
and deleting it from your system.
This information may be exempt from disclosure under Freedom Of Information 
Act 2000 and may be subject to exemption under other UK information 
legislation. Refer disclosure requests to the Information Officer
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________