3 ms·
> URL-safe-base64 And make sure to specify what exactly you mean by that. base64url-encoding is incompatible with base64+urlencoding in ~3% of cases, which is
by johnp_ 2y ago
> URL-safe-base64
And make sure to specify what exactly you mean by that. base64url-encoding is incompatible with base64+urlencoding in ~3% of cases, which is easily missed during development, but will surely happen in production.
- Retr0id 2y agoIsn't it a lot more than 3%? I don't think I've heard anyone say url-safe-base64 and actually mean urlencode(base64(x))
- deathanatos 2y ago… yeah. I assume they're getting that from doing 3/64, but for uniform bytes, you're rolling that 3/64 chance every base64-output-character. (And bytes are hardly uniform, either … TFA's example input of JSON is going to skew towards that format's character set.)
- deathanatos 2y agooh, geez. No, just base64, using the URL safe alphabet. (The obvious 62 characters, and "-_" for the last two. It's called "urlsafe base64", or some variant, in the languages I work in. > This encoding may be referred to as "base64url". https://datatracker.ietf.org/doc/html/rfc4648#section-5 https://datatracker.ietf.org/doc/html/rfc4648#section-5 But yeah, it's not base64 followed by a urlencode. It's "just" base64-with-a-different-alphabet.