W3C home > Mailing lists > Public > uri@w3.org > January 2010

Re: When is percent-encoding required.

From: Bob Aman <sporkmonger@gmail.com>
Date: Sun, 10 Jan 2010 10:31:05 -0800
Message-ID: <81c242241001101031g68d16770g2ba2ed0efa2e89be@mail.gmail.com>
To: Charles Lindsey <chl@clerew.man.ac.uk>
Cc: Julien ÉLIE <julien@trigofacile.com>, URI <uri@w3.org>
>>> When I said "URI parsers" I specifically meant the parser itself — as
>>> in, the parser won't misinterpret some component as something other
>>> than what it is, and the value of all components will be available to
>>> the application.  As Martin said, those characters aren't really
>>> supposed to show up in a URI and have to be encoded.  Browsers that
>>> figure out what you meant and encode the URI before sending it are
>>> following Postel's law and, in my opinion, doing the right thing.
>> I do not know what browsers are supposed to do but if that is the
>> right thing, then it does not work with the NNTP protocol.
> But nobody is expecting it to be sent to NNTP in that form. Whoever/whatever
> interprets that URI (possibly a browser) should decode it, then open an NNTP
> dialog with the NNTP server, and then send the article with the funny
> characters already decoded. Perhaps I should mention that in the RFC.

Exactly.  And yes, I would be inclined to make it explicit.

Received on Sunday, 10 January 2010 18:31:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:13 UTC