URL path parameters

According to RFC 2396 (which claims at the top to obsolete RFC 1738)
section 3.3, *every* URL path segment may have a list of parameters.
I believe the neturl code allows only one path parameter list, after
the last path segment.

Now, I've never seen a case "in the wild" where this bizarre feature
of the URL spec is actually used, but I think it would be good if
neturl dealt with it gracefully.

A simple test case is:

  http://foo/hello%3B;%3B;/there

When passed through a string->url->string cycle, the escaped
semicolons must remain escaped, and the unescaped semicolons must
remain unescaped.  When fetching the unescaped path from the url, one
should get ["hello;"; "there"].

Perhaps my reading of the RFC is incorrect?

  Alan




-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php