Re: fnord bugs I found + new httpd (was: A fnord fork (a fnork?))

--Boundary-00=_AfhbPzoST6Frn0N
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Am Dienstag, 20. M=C3=A4rz 2012, 23:20:52 schrieb Neale Pickett:
>=20
> # 3. Should process both requests; instead drops second

I already reported this one in 2005.
See below for Felix's anwser, which probably also applies to
your problem #7.

> # 7. HTTP/1.1 should default to keepalive; instead connection is closed

Bye,
	Peter
=2D-=20
Peter Conrad                        Tel: +49 6102 / 80 99 072
[ t]ivano Software GmbH             Fax: +49 6102 / 80 99 071
Bahnhofstr. 18                      http://www.tivano.de/
63263 Neu-Isenburg

Germany

--Boundary-00=_AfhbPzoST6Frn0N
Content-Type: message/rfc822;
  name="forwarded message"
Content-Transfer-Encoding: 7bit
Content-Description: Felix von Leitner <[email protected]>: Re: Various fnord patches
Content-Disposition: inline

Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 25081 invoked by uid 3003); 22 Dec 2005 11:00:08 -0000
Received: from 80.190.240.67 by bradbury (envelope-from <[email protected]>, uid 501) with qmail-scanner-1.25 
 (clamdscan: 0.86.2/1003. trophie: 7.510-1002/755/105672. spamassassin: 3.0.4.  
 Clear:RC:0(80.190.240.67):SA:0(1.2/5.0):. 
 Processed in 5.424177 secs); 22 Dec 2005 11:00:08 -0000
X-Spam-Status: No, hits=1.2 required=5.0
X-Spam-Level: +
Received: from ipx10069.ipxserver.de (HELO codeblau.de) (80.190.240.67)
  by bradbury.tivano.net with SMTP; 22 Dec 2005 11:00:03 -0000
Received: (qmail 14777 invoked by uid 1000); 22 Dec 2005 10:59:42 -0000
Mailing-List: contact [email protected]; run by ezmlm
Delivered-To: mailing list [email protected]
Received: (qmail 14770 invoked by uid 1000); 22 Dec 2005 10:59:42 -0000
Date: Thu, 22 Dec 2005 11:59:42 +0100
From: Felix von Leitner <[email protected]>
To: [email protected]
Subject: Re: Various fnord patches
Message-ID: <[email protected]>
Mail-Followup-To: [email protected]
References: <[email protected]> <[email protected]> <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>
User-Agent: Mutt/1.5.11
Content-Length: 710
Lines: 15

Thus spake Peter Conrad ([email protected]):
> > > 6. Another potential request smuggling problem
> [...]
> > fnord does not support pipelining.  AFAIK this is perfectly legal.
> I don't think so. RFC 2616 section 8.1.1 mentiones pipelining as one
> purpose of persistent connections. More specifically, section 8.1.2.2 says

That's HTTP/1.1.  Fnord is not actually a HTTP/1.1 web server.  It also
does not support chunked encoding, for example.  Fnord supports some
aspects of HTTP/1.1, but that's it.  Note that a client can not know
whether a server supports HTTP/1.1 before sending the request, thanks to
proxies and load balancers not even if a previous request was answered
as supporting HTTP/1.1.

Felix

--Boundary-00=_AfhbPzoST6Frn0N--