On Fri, 24 Aug 2001, Larry Isaacs wrote:
> In case in matters, RFC 1630 states that:
>
> PATH
>
> The rest of the URI follows the colon in a format
> depending on the scheme. The path is interpreted
> in a manner dependent on the protocol being used.
> However, when it contains slashes, these must
> imply a hierarchical structure
>
> I read this as meaning the slashes in "http://fubar"; are
> required to be encoded. Page 9 of RFC 1630 contains
> "Example 2", which illustrates this.
> Since Tomcat 3.3
> and Tomcat 4.0 also disallow "%2F", we all have this issue.
That's the only point I disagree with.
We are able to allow %2F and other encoding. This
is however risky ( 3.3 had this behavior - we changed it
only for consistency with 3.2 and 4.0 ).
Costin
