Use strict_encode64 for basic authentication
#325
Closed
Conversation
This file contains hidden or 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
Member
|
But the gem does not support this old ruby version anymore. 👍 Could you apply this change to every calls of the method ? |
Member
|
We will definitely not be supporting Ruby 1.8. Need to think about support for other EOL'd Rubies. |
Contributor
Author
|
Totally. I’m on it! |
Member
|
FYI the rubocop offenses are fixed. So the Travis build should pass when you will push. |
Member
|
@erik-escobedo ping! |
Member
|
This change was merged in #414 |
pboling
added
in Changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Base64.strict_encode64method doesn't need to remove the"\n"characters a posteriori.