Add support for RFC 4648 base64url encoding #3380
Open
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.
RFC 4648 provides an alternate encoding alphabet using -_ in place of +/ to assist in produce encoded strings which do not require % encoding for including in urls. The nodejs Buffer class supports this encoding for example.
This change adds support for encoding in base64url with padding included (base64urlp) and with padding excluded (base64url). The latter is provided and named to mimic the nodejs version of this encoding.
This change permits base64d to decode either base64 or base64url. This also mimics nodejs which decodes both in either encoding.
Also, add docs and tests for this change.