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
In addition, can we consider to optimize the encoder by avoiding to first convert to Base64 then replace to url-safe character. instead, convert directly to Base64Url, simply by changing the Base64 character map and by removing the padding?
From @ycrumeyrolle on Wednesday, June 7, 2017 5:42:43 AM
https://github.com/aspnet/Common/blob/dev/shared/Microsoft.Extensions.WebEncoders.Sources/WebEncoders.cs
https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.WebUtilities/Base64UrlTextEncoder.cs
Related #93
In addition, can we consider to optimize the encoder by avoiding to first convert to Base64 then replace to url-safe character. instead, convert directly to Base64Url, simply by changing the Base64 character map and by removing the padding?
Copied from original issue: dotnet/extensions#237
The text was updated successfully, but these errors were encountered: