You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.
"The following functions perform base64url encoding which differs from regular base64 encoding as follows
padding is skipped so the pad character '=' doesn't have to be percent encoded
the 62nd and 63rd regular base64 encoding characters ('+' and '/') are replace with ('-' and '_') The changes make the encoding alphabet file and URL safe."
The text was updated successfully, but these errors were encountered:
z2z
changed the title
Feature Request: Make it the has URL Safe
Feature Request: URL Safe
May 8, 2021
Sorry for the late response, I've been busy. I don't think we need this feature, it will break backwards compatibility without offering any significant benefits. Besides, it's not that hard to change the encoding format, before and after decrypt/encrypt operations.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add something like Base64url
Ref: https://docs.microsoft.com/en-us/dotnet/api/microsoft.identitymodel.tokens.base64urlencoder.encode?view=azure-dotnet#Microsoft_IdentityModel_Tokens_Base64UrlEncoder_Encode_System_String_
"The following functions perform base64url encoding which differs from regular base64 encoding as follows
padding is skipped so the pad character '=' doesn't have to be percent encoded
the 62nd and 63rd regular base64 encoding characters ('+' and '/') are replace with ('-' and '_') The changes make the encoding alphabet file and URL safe."
The text was updated successfully, but these errors were encountered: