- From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
- Date: Fri, 21 Mar 2014 12:29:51 +0100
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: "Nicolas Mailhot" <nicolas.mailhot@laposte.net>, "Mark Nottingham" <mnot@mnot.net>, "HTTP Working Group" <ietf-http-wg@w3.org>, "Gabriel Montenegro" <gabriel.montenegro@microsoft.com>
Le Ven 21 mars 2014 12:01, Julian Reschke a écrit : > On 2014-03-21 11:55, Nicolas Mailhot wrote: > That seems to be the same use case as #1. > > Why don't you just try to UTF-8 decode, and if that works, assume that > it indeed is UTF-8? Really, can't you read the abundant documentation that was written on the massive FAIL duck typing is for encoding (for example, python-side)? Code passing unit tests then failing right and left as soon as some new encoding combo or text triggering encoding differences injected in the system? Piles of piles of partial workarounds till there was complete loss of understanding how they were all supposed to work in the first place? That's the last thing you want to reinvent on security equipments (and you'll reinvent it because the amount of non-ASCII urls is small now but will only grow with time). -- Nicolas Mailhot
Received on Friday, 21 March 2014 11:30:37 UTC