W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Re: draft-montenegro-httpbis-uri-encoding

From: Mike Belshe <mike@belshe.com>
Date: Fri, 21 Mar 2014 06:10:50 -0700
Message-ID: <CABaLYCs9ZeTNk2COHsE6sqZ7PG=+j_GVDmYv3Mjdm0jLkdbOJQ@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: Nicolas Mailhot <nicolas.mailhot@laposte.net>, Julian Reschke <julian.reschke@gmx.de>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>, Gabriel Montenegro <gabriel.montenegro@microsoft.com>
On Fri, Mar 21, 2014 at 5:54 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

> * 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.

I too am wondering this.

In general, this just sounds like "more stuff".

I'm not aware of anyone having real-world problems which this solves. It
would be very helpful if those real cases were enumerated.


> --
> 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 13:11:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:25 UTC