Add option to unescape or not during SIP URI parsing #4042
Closed
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
trengginas
reviewed
Aug 19, 2024
| @@ -404,7 +408,13 @@ static pj_status_t pjsip_url_compare( pjsip_uri_context_e context, | |||
| * This includes userinfo containing passwords or formatted as | |||
| * telephone-subscribers. | |||
| */ | |||
| if (pj_strcmp(&url1->user, &url2->user) != 0) | |||
| str[0].ptr = buf[0]; | |||
There was a problem hiding this comment.
Should it protect this with PJSIP_UNESCAPE_WHEN_PARSING_URI when comparing unescape user part?
|
A different approach was adopted in #4043. |
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.
No description provided.