Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Given following code:
XmlResolver res = new XmlUrlResolver();
var uri = res.ResolveUri(null, "view:Standard.xslt");
// .NET outputs:
// Mono on Linux outputs:
// Mono on Windows outputs:
Created attachment 478 [details]
bug fix for review.
Rather than just checking http, https, ftp, file allow any specified scheme.
Thanks for the report. I made a fix in git master 82f61e9 (in somewhat different approach).
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 relative URI strings 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 (when the relative file path began with "http:foobar" etc.)