We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Equality tests against NamespaceUris are exact string matches. The Uri class can normalize Uris and result in false positives or false negatives.
The text was updated successfully, but these errors were encountered:
Equality tests in the Server should be done with Uri.OriginalString https://learn.microsoft.com/en-us/dotnet/api/system.uri.originalstring?view=net-6.0
The documentation should have a discussion of the need to use Uri.OriginalString when testing for equality inside client applications.
Sorry, something went wrong.
MarkusHorstmann
Successfully merging a pull request may close this issue.
Equality tests against NamespaceUris are exact string matches.
The Uri class can normalize Uris and result in false positives or false negatives.
The text was updated successfully, but these errors were encountered: