Regarding the checking "Standards.URI: More paranoid handling of ..-segments that reach past the root.": Is the semantics of the path segment declared somewhere? If not we shouldn't probably do sanity checking/normalization of it in Standards.URI.
From the comment just before:
// g) If the resulting buffer string still begins with one or more // complete path segments of "..", then the reference is // considered to be in error. Implementations may handle this // error by retaining these components in the resolved path (i.e., // treating them as part of the final URI), by removing them from // the resolved path (i.e., discarding relative levels above the // root), or by avoiding traversal of the reference.
Which seems to be from RFC 2396, §5.2.6.
pike-devel@lists.lysator.liu.se