[CoreHttp] Add strncasecmp implementation #106
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yourslab
reviewed
Jul 8, 2021
yourslab
reviewed
Jul 8, 2021
yourslab
reviewed
Jul 8, 2021
yourslab
reviewed
Jul 8, 2021
yourslab
reviewed
Jul 8, 2021
yourslab
reviewed
Jul 8, 2021
yourslab
reviewed
Jul 8, 2021
yourslab
previously approved these changes
Jul 9, 2021
Co-authored-by: Muneeb Ahmed <[email protected]>
yourslab
reviewed
Jul 9, 2021
archigup
previously approved these changes
Jul 9, 2021
gkwicker
suggested changes
Jul 10, 2021
gkwicker
approved these changes
Jul 10, 2021
archigup
approved these changes
Jul 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the implementation for strncasecmp function as strncasecmp is not a standard C function and is not compatible across different platforms. This fix is needed as a result of change contributed by external PR to have case insensitive matching of field name in the header as header field consists of a case-insensitive field name (RFC 7230, section 3.2).