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
2 times, most recently
from
38d3044
to
a3ce3eb
Compare
dg
force-pushed
the
master
branch
2 times, most recently
from
38cc5db
to
0a8a17e
Compare
dg
force-pushed
the
master
branch
5 times, most recently
from
4b7b01e
to
494d200
Compare
dg
force-pushed
the
master
branch
5 times, most recently
from
b843c77
to
77e9645
Compare
dg
force-pushed
the
master
branch
7 times, most recently
from
7ae8df7
to
0d1508c
Compare
dg
force-pushed
the
master
branch
3 times, most recently
from
5b5c893
to
81e3e6d
Compare
dg
force-pushed
the
master
branch
2 times, most recently
from
b080db7
to
d668e02
Compare
dg
force-pushed
the
master
branch
4 times, most recently
from
1e73622
to
d6a9961
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.