- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Fri, 21 Mar 2014 13:54:04 +0100
- To: "Nicolas Mailhot" <nicolas.mailhot@laposte.net>
- Cc: "Julian Reschke" <julian.reschke@gmx.de>, "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>
* Nicolas Mailhot wrote: >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). Julian asked for a concrete example use case. So far you have not given one. It might help to assume the rest of us understands the subject at hand at least as well as you do. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Friday, 21 March 2014 12:54:36 UTC