Breaking change to Uri.IsWellFormedUriString in .NET 4.5 - by pattermeister

Status : 

  Accepted<br /><br />
		The product team has accepted this issue and will be determining when the issue will be addressed.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 778454 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 2/4/2013 4:48:15 AM
Access Restriction Public

Description

Uri.IsWellFormedUriString appears to have changed behaviour in a way that I can't see documented on the breaking changes list.

I am trying to understand whether this change could have caused this issue, but I don't think it is:

"Unicode normalization form C (NFC) will no longer be performed on non-host portions of URIs. Previously, NFC was performed on the entire URI when <iriParsing> was enabled."
Sign in to post a comment.
Posted by Microsoft on 5/31/2013 at 9:58 AM
We regret that we will be unable to take ths bug at this time. In general, Uri changes -- even when they are intended to improve our compliance with the RFCs -- will result in breaking changes. We made a number of changes to our Uri parsing in 4.5; as you've noted, some of these cause issues.
Posted by pattermeister on 4/16/2013 at 1:27 AM
When can I expect this to be triaged?
Posted by Microsoft on 2/4/2013 at 11:40 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 2/4/2013 at 4:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)