Fix bug 998 - in XmlResolver.ResolveUri(), make some policy change on "how to determi...
authorAtsushi Eno <atsushi@ximian.com>
Thu, 19 Jan 2012 11:45:42 +0000 (20:45 +0900)
committerAtsushi Eno <atsushi@ximian.com>
Thu, 19 Jan 2012 11:45:42 +0000 (20:45 +0900)
commit82f61e9074d85129cf7d23c768af03149f0a2d74
tree51444e89fac4cd00682c112161362330a2884ef5
parente642e68ad803a4cfa3bff6166a89d558f1e02766
Fix bug 998 - in XmlResolver.ResolveUri(), make some policy change on "how to determine a string as an absolute URI.

It's a bit difficult decision, as the "relative URI" could be any path string
that contain colons as a *valid* path (especially on *nix land).
We historically did allow such string that contain "http:" etc. as to be
treated as absolute (which historically worked long time).
But this test case uncovered possible other cases.
Hopefully this does not bring issues that is pretty much anticipated. Such
issues could also happen in older code anyways.
mcs/class/System.XML/System.Xml/XmlResolver.cs
mcs/class/System.XML/Test/System.Xml/XmlUrlResolverTests.cs