2884 2006-02-16 17:57:07 +0000 fn-resolve-uri-3 2006-06-22 13:02:08 +0000 1 1 1 Unclassified XML Query Test Suite XML Query Test Suite 0.8.4 PC Linux CLOSED FIXED P2 normal --- 1 simeon carmelo oldest_to_newest 8291 0 simeon 2006-02-16 17:57:07 +0000 "http://" seems to be a valid URI as far as I can tell. The RFC says that the authority can be absend and the path can be empty in the following: URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] hier-part = "//" authority path-abempty ... The scheme and path components are required, though the path may be empty (no characters). When authority is present, the path must either be empty or begin with a slash ("/") character. When authority is not present, the path cannot begin with two slash characters ("//"). These restrictions result in five different ABNF rules for a path (Section 3.3), only one of which will match any given URI reference. And my URI library actually accepts it. I'm not an expert here, though... Any feedback would be appreciated. - Jerome 8314 1 andrew.eisenberg 2006-02-17 19:37:43 +0000 I believe that your argument for the validity of http:// is based on RFC 2396. RFC 3986 differs, requiring that host be specified: URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] hier-part = "//" authority path-abempty / path-absolute / path-rootless / path-empty authority = [ userinfo "@" ] host [ ":" port ] host = IP-literal / IPv4address / reg-name So, what we need a URI that bith RFCs agree is invalid. 8637 2 carmelo 2006-03-08 19:23:30 +0000 How about: http// 8666 3 carmelo 2006-03-10 20:15:19 +0000 Jerome: Made the URI invalid by removing the ":", please close the bug if in agreement and able to verify. Carmelo