DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34937>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34937 ------- Additional Comments From [EMAIL PROTECTED] 2005-05-16 21:14 ------- If I understand it correctly, RFC 3986 (like RFC 2396 before it) mandates (or at least strongly suggests) in section 3 at least two slashes after the scheme component ("file:" in this case) of a URI. The third, which precedes the URI's absolute path, also marks the end of any "authority" (a domain or subdomain in HTTP URLs). Furthermore, RFC 3986 uses "file:///etc/hosts" as an example URI in section 1.1. So it looks to me like "file:/sample.xml" is an invalid URI. If this is correct, the obvious questions are 1) how to get non-conformant implementations conformant, and 2) what, if anything, XSEC C++ should do differently when it gets an invalid URI. Of course, if my understanding is wrong, so are my questions. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
