- From: <nicolas.mailhot@laposte.net>
- Date: Tue, 12 Jul 2016 15:31:45 +0200 (CEST)
- To: Willy Tarreau <w@1wt.eu>
- Cc: Julian Reschke <julian.reschke@gmx.de>, Poul-Henning Kamp <phk@phk.freebsd.dk>, Yanick Rochon <yanick.rochon@gmail.com>, Phil Hunt <phil.hunt@oracle.com>, HTTP Working Group <ietf-http-wg@w3.org>
> OK thanks for explaining. But then what situation could lead to this > confusing object to be emitted ? I suppose that this can happen in pipelined architecture where each processing step thinks it owns a header and does not check if another step didn't already set it before IE when you mashup loads of third-party javascript and hope the resulting soup will work
Received on Tuesday, 12 July 2016 13:32:11 UTC