From owner-freebsd-hackers Mon Jan 29 02:05:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA18523 for hackers-outgoing; Mon, 29 Jan 1996 02:05:31 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA18517 for ; Mon, 29 Jan 1996 02:05:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id CAA29539; Mon, 29 Jan 1996 02:04:06 -0800 Message-Id: <199601291004.CAA29539@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Luigi Rizzo cc: hackers@freebsd.org Subject: Re: Why RFC1323 is disabled on freefall and freebsd.cdrom.com ? In-reply-to: Your message of "Mon, 29 Jan 1996 10:42:14 +0100." <199601290942.KAA05121@labinfo.iet.unipi.it> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 29 Jan 1996 02:04:06 -0800 Sender: owner-hackers@freebsd.org Precedence: bulk >I was wondering why RFC1323 timestamps are disabled on both freefall >and freebsd.cdrom.com > >I know one reason not to have them is that they defeat VJ header >compression, but I don't see the point in having them disabled on >freebsd.cdrom.com > >If there are no good reasons, could they be enabled ? It is disabled on both machines because they are public FTP/WWW servers, and RFC1323 (and other TCP extensions) don't work for all people. It will remain disabled until such time that 99.999% of the people out there can deal with TCP extensions. Otherwise, we'll be getting way too many bug reports. Wcarchive, for example, serves 20000 people a day; I'm sure you can imagine the extremely high probability that more than one person per day will run into this problem. :-) -DG David Greenman Core Team/Principal Architect, The FreeBSD Project