Fix proxy authorization #147
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
hyperioxx
reviewed
Nov 4, 2022
|
it should be fixed now :D |
hyperioxx
approved these changes
Nov 5, 2022
|
How to hande 401 (Unauthorized) code on INVITE with WWW-Authenticate, which requires Authorization header? As I understand from rfc3261, response may include Authorization value for each WWW-Authenticate value and a Proxy-Authorization value for each Proxy-Authenticate value. So if UAC receive 401 with WWW-Authenticate Kalbi will answer with Proxy-Authenticate, which is invalid in this case. |
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.
Response requires different Authorization filed on INVITE than on REGISTER.
We tested it on Kamailio SIP Proxy