On Fri, Feb 11, 2005 at 01:05:53PM -0500, Jim W. Jaszewski wrote: > I have no idea what's happening with this one. This is the only URL I > access which has ever given this particular error, and it used to work > just fine previously. For all I know, it'll work just fine on other > machines. I believe this problem has been ongoing for months, so it's > not an intermittent thing.
Thanks for the report. Indeed, this is a problem with one of the latest security patches that unintentionally now also caps the receive buffer to smaller values than before. This is easily fixed, though, and I'll provide an update soon. Regards, Daniel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
