Describe the issue or suggestion
Direct link to the XmlDoc
This property does not restrict setting the property to these values as this remarks section claims (which is a good thing) and in fact has not done that for a long time.
Instead, the set accessor validates input according to RFC 2396, when it calls System.Uri.CheckSchemeName, which will allow any valid sequence of characters that is legal as a URI scheme according to the RFC.
This has been true at least since .net 5, with its earlier form of the System.Uri.CheckSchemeName method.
So this remarks section should probably just go away or change to saying that the set accessor validates according to RFC 2396 (though that could also just be in the summary, instead).
Non-permalink forms of the above links, to the tags they came from:
Describe the issue or suggestion
Direct link to the XmlDoc
This property does not restrict setting the property to these values as this remarks section claims (which is a good thing) and in fact has not done that for a long time.
Instead, the set accessor validates input according to RFC 2396, when it calls System.Uri.CheckSchemeName, which will allow any valid sequence of characters that is legal as a URI scheme according to the RFC.
This has been true at least since .net 5, with its earlier form of the System.Uri.CheckSchemeName method.
So this remarks section should probably just go away or change to saying that the set accessor validates according to RFC 2396 (though that could also just be in the summary, instead).
Non-permalink forms of the above links, to the tags they came from: