- From: Zhong Yu <zhong.j.yu@gmail.com>
- Date: Tue, 21 Apr 2015 10:24:47 -0500
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: "Roy T. Fielding" <fielding@gbiv.com>, Barry Leiba <barryleiba@computer.org>, RFC Errata System <rfc-editor@rfc-editor.org>, Pete Resnick <presnick@qti.qualcomm.com>, Mark Nottingham <mnot@mnot.net>, Simon Schüppel <simon.schueppel@googlemail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Another question about obs-fold before we proceed with the formal definitions. Consider the following example foo: bar<CRLF> <SP><CRLF> ... It won't be surprising if some parser mistakes the 2nd line as an "empty line" that terminates the headers. Visually it *is* an empty line. In spirit, obs-fold should be followed by visible chars, otherwise it's very confusing and problematic. RFC 822 $3.2 appears to suggest the same thing, that obs-fold can only appear between two non-empty segments. Zhong
Received on Tuesday, 21 April 2015 15:25:15 UTC