W3C home > Mailing lists > Public > uri@w3.org > November 2002

Re: Ambiguity of Allowed/Recommended URI Syntax and Escaping

From: Roy T. Fielding <fielding@apache.org>
Date: Sun, 17 Nov 2002 23:50:33 -0800
Cc: Terje Bless <link@pobox.com>, URI List <uri@w3.org>
To: Jim Correia <correia@barebones.com>
Message-Id: <6AF7F75F-FACA-11D6-8A85-000393753936@apache.org>

> Under what situations is it encouraged that a URI generated escape those 
> reserved characters in the query?

At any time that the character is considered data instead of a delimiter
of significance to the generator.

> For example, given the URI
>
> http://www.example.com/redir?uri=http://www.example.com/someplace/else/
>
> is it suggested that the : and / be escaped for good practice/robustness?

Yes (see note regarding "/" in query).

>  According to the spec, is it valid for them to be left un-escaped?

Yes, since only the generator knows why they are being used.

> (In the context of the query, what is the meaning of the reserved purpose?
>  The usual reserved purpose of / is as a hierarchy separator, and when 
> used as data in the query part it is no longer a hierarchy separator, 
> correct?)

The generic syntax does not consider it as a hierarchy separator in
the query.  However, that does not prevent the URI generator from
considering it a hierarchy separator, or even a foo-bar separator.
The purpose of reserved characters is to give components some characters
that can be safely used as delimiters within that component.  Whether
or not the generator uses those characters is unknown, and doesn't
matter to other parsers.

....Roy
Received on Monday, 18 November 2002 14:30:07 UTC

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