Date: Wed, 30 Apr 1997 12:12:13 -0700 (PDT)
From: Dean Gaudet <dgaudet@arctic.org>
To: new-httpd@apache.org
Subject: Re: [PATCH] PR#232: work around netscape header problem 
In-Reply-To: <Pine.BSF.3.95q.970430124452.14004H-100000@valis.worldgate.com>
Message-ID: <Pine.LNX.3.95dg3.970430121125.3621G-100000@twinlark.arctic.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

As far as I know it has been sent to their internal bugs list and Lou.  I
used another contact I had to get it "past the front door".  That's
probably the best we can hope for.  It's probably beside the "fix
x-byteranges" bug ;) 

Dean

On Wed, 30 Apr 1997, Marc Slemko wrote:

> So, someone want to pick someone else at Netscape to whine at
> about it?  I have had no response and haven't had a chance
> to pester yet...
> 
> On Fri, 18 Apr 1997, Roy T. Fielding wrote:
> 
> > 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).
> > 
> > I took Dean's patch and removed the BrowserMatch (it would match almost
> > all browsers anyway) and made it apply to all places where we terminate
> > headers.  I also verified that it prevents the bug on Netscape 3.01.
> 
>