API: Add LRO_USERNAME and LRO_PASSWORD options #316
Merged
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.
The original
LRO_USERPWD
option does not support a colon in the username. UseLRO_USERNAME
andLRO_PASSWORD
instead.The description of the
LRO_USERPWD
option has been expanded:The user and password strings are not URL decoded, so there is no way to send in a username containing a colon using this option. The option is DEPRECATED!
Use LRO_USERNAME and LRO_PASSWORD.
The description of the
LRO_PROXYUSERPWD
option has been expanded:Both the username and the password are URL decoded before use, so if the username contains, for example, a colon, it should be encoded as %3A.
Unit tests for
LRO_USERNAME
andLRO_PASSWORD
are included.Closes: #315