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
The encode and decode SQL functions only support base64 encoding. The problem with that is that base64 uses characters that have meaning in URLs, ie + and /. A derived encoding base64URL replaces + with -, and / with _, which are both characters without need for url encoding. Thus I would like to propose to add base64URL as a format.
I think this shouldn't be too hard, as in the resulting encoding or passed encoded string the characters in question would just have to be replaced before decoding or after encoding with base64.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The
encodeanddecodeSQL functions only supportbase64encoding. The problem with that is that base64 uses characters that have meaning in URLs, ie+and/. A derived encodingbase64URLreplaces+with-, and/with_, which are both characters without need for url encoding. Thus I would like to propose to add base64URL as a format.I think this shouldn't be too hard, as in the resulting encoding or passed encoded string the characters in question would just have to be replaced before decoding or after encoding with
base64.All reactions