I am not at all sorry if upgrading to the current STABLE version fixed your problem, only glad! In fact, I assumed you were already running 2.5.STABLE1 as you did not tell which version you were using..
If you had filed a bug report for Squid-2.4 the first response to the bug report would anyway have been "upgrade to 2.5.STABLE1 or later, if the problem reoccurs with the current STABLE version please return" as Squid-2.4 is no longer maintained or bug fixed. Regards Henrik On Friday 21 February 2003 02.01, SSCR Internet Admin wrote: > I am sorry to tell you that i have upgraded my squid-2.4STABLE7 to > squid-2.5.STABLE1 which really fix the problem. I dont know if ill > meet this in the near future, and i have not set the coredump_dir, > tsk tsk.. ill see to it ill send a bug report once this problem > occurs again > > -----Original Message----- > From: Henrik Nordstrom [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 20, 2003 12:01 AM > To: SSCR Internet Admin; squid-mailing list > Subject: Re: [squid-users] Unsupported Methods Found on cache.log > > On Thursday 20 February 2003 18.16, SSCR Internet Admin wrote: > > Hi, > > > > Im having lots of this on cache.log - unsupported method > > 'MachineId:.. blahblah...' and followed by ClientReadRequest : > > FD36 Invalid Request, > > Looks like a client sending a malformed request to Squid. > > Are you running Squid as a normal proxy or transparently > intercepting port 80? > > > and if it continues i got FATAL : Recevied > > Segmentation Fault.. Dying... > > Please get a stack trace of the segmentation fault and report a > Squid bug in our bug management tool (bugzilla). Squid should not > segmentation fault. > > For details on how get a stack trace and to register a bug see > "Squid FAQ 11.19 Sending in Squid bug reports" > <url:http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19> > > Regards > Henrik
