- From: Willy Tarreau <w@1wt.eu>
- Date: Sat, 17 Dec 2011 08:40:46 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Alex Rousskov <rousskov@measurement-factory.com>, HTTP Working Group <ietf-http-wg@w3.org>
Hi Julian, On Sat, Dec 17, 2011 at 01:02:21AM +0100, Julian Reschke wrote: > Will those servers process > > ,100-continue > > or > > 100-continue, > > ? These were valid before already. Speaking for haproxy, the second one will work, because it splits header values on the commas and trims the spaces. So the first above will be considered as an empty expectation followed by a 100-continue (but haproxy only considers the first Expect value) and the second one is OK. Haproxy's processing of Expect is incomplete and almost unused, so it should not be seen as a reference implementation at all (!). However the semi-colon after 100-continue was not supposed to happen in 2616, which is why I think other implementations might get trapped. Regards, Willy
Received on Saturday, 17 December 2011 07:41:17 UTC