- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Wed, 23 Nov 2016 16:51:14 +0900
- To: Julian Reschke <julian.reschke@gmx.de>, Martin Thomson <martin.thomson@gmail.com>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2016/11/23 15:15, Julian Reschke wrote: > On 2016-11-23 01:47, Martin Thomson wrote: >> The virtue of this is that a particular profile can define this field >> as it chooses, to meet its own requirements. If you intend to use >> this with strings, then you can constrain to ASCII or UTF-8 as you see >> fit. >> ... > > I see lot of additional works and potential bugs by allowing non-UTF-8 > octet sequences, and something like zero advantages. Yes indeed. Not knowing what character encoding is used for a string, or not knowing whether something is binary or text, it a lot of pain, and no "virtue" at all. We have a lot of experience with that; let's not repeat these same mistakes over and over again. Regards, Martin.
Received on Wednesday, 23 November 2016 07:51:57 UTC