Skip to content

Fixed matching URL path to service type in Extensibility.AuthorizeOperationMessageProcessor #1140

New issue

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

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

SerbanApostol
Copy link

Previously, the caller of the constructor had the responsibility to make the path for the service to be lowercase. I modified the constructor to make the path lowercase as it is not obvious to the caller that this is necessary.

Serban Apostol added 3 commits May 12, 2025 13:02
When the dictionary on the constructor of Extensibility.AuthorizeOperationMessageProcessor had its keys not all lowercase, it couldn't find the service type and, consequently, the operation
When the dictionary on the constructor of Extensibility.AuthorizeOperationMessageProcessor had its keys not all lowercase, it couldn't find the service type and, consequently, the operation
@andersjonsson
Copy link
Collaborator

There is an option to make path insensitive (SoapCoreOption.CaseInsensitivePath). Would it be a good idea to use that to decide if comparison should be case-insensitive?

Dictionary accepts a comparer in the constructor new Dictionary<string, Type>(StringComparer.OrdinalIgnoreCase) that makes it easy to vary behavior depending on the option

@SerbanApostol
Copy link
Author

Thank you for pointing me to the option of supplying a comparer to Dictionary<,>. I removed the foreach that made each key lowercase and instead used the comparer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants