Strings: add base64UrlEncode() and base64UrlDecode() #287
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
…turn objects Type (BC break)
Since PHP 8.0 ReflectionParameter::getDefaultValue() correctly returns value or throws exception when constant cannot be resolved
dg
force-pushed
the
master
branch
10 times, most recently
from
6733224 to
5de10a1
Compare
dg
force-pushed
the
master
branch
16 times, most recently
from
a846fab to
736c567
Compare
dg
force-pushed
the
master
branch
2 times, most recently
from
cd9170e to
2b48b24
Compare
dg
force-pushed
the
master
branch
2 times, most recently
from
6f1918e to
be53471
Compare
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.
Base64 encoding is well known. It uses alphabet of 64 chars
A-Z a-z 0-9 + /and padding char=. While theA-Z a-z 0-9chars are URL safe, the remaining+ / =are not. So there is a "Base 64 Encoding with URL and Filename Safe Alphabet" as mentioned in RFC4648. This encoding replaces+by-and/by_and drops=padding.The base64Url encoding is for example used by JSON Web Tokens (JWT), which are used for example in Open ID Connect protocol.
The implementation is based on Appendix C of IETF draft.