Received: (from majordom@localhost) by hyperreal.com (8.8.4/8.8.4) id IAA18664; Fri, 18 Apr 1997 08:00:41 -0700 (PDT) Received: from DECUS.Org (Topaz.DECUS.Org [192.67.173.1]) by hyperreal.com (8.8.4/8.8.4) with ESMTP id IAA18660 for ; Fri, 18 Apr 1997 08:00:39 -0700 (PDT) Received: from Lucy.DECUS.Org (lucy.process.com) by DECUS.Org (PMDF V4.2-13 #18511) id <01IHUJT79WIO8WYHAS@DECUS.Org>; Fri, 18 Apr 1997 10:54:25 EST Received: from master.process.com by Lucy.DECUS.Org; (5.65v3.2/1.1.8.2/16Sep96-0258PM) id AA25140; Fri, 18 Apr 1997 10:57:56 -0400 Date: Fri, 18 Apr 1997 10:42:07 -0400 From: coar@decus.org (Rodent of Unusual Size) Subject: Re: [PATCH] PR#232: work around netscape header problem To: New-HTTPd@apache.org, Coar@decus.org Message-id: <97041810420748@decus.org> X-VMS-To: NH X-VMS-Cc: COAR Content-transfer-encoding: 7BIT Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org >From the fingers of "Roy T. Fielding" flowed the following: > >After thinking about this a while, I've changed my mind and now believe >that we need to fix Netscape's bug for them. The reasons are that the >bug is non-intuitive to non-programmers, we'll end up getting blamed >for it anyway, I have a feeling that Netscape won't get around to >fixing it in 4.0, and my fix has no impact unless the headers are >exactly 256 or 257 bytes long (the bug manifests in both cases). +1 if you change the wimpy pad header message to something more robust like "X-Pad: Massive network bandwidth consumption required to work around lame brain-damage in Netscape's Mozilla". {Only kidding..} How about "X-Pad: You are not expected to understand this"? :-> +1 in concept, but untested (other than it compiles fine). #ken :-)}