Comprendre Base64 Padding
Profond dive into why Base64 uses = padding, how it works, and when you can safely strip it.
问题
You see one ou two '=' caractères at le fin de Base64 sortie et vouloir en understand leurs objectif et quand they peut être removed.
Prérequis
- Basic Base64 encoding knowledge
- Understanding of bit-level data representation
Étapes
-
1. Review the 3-to-4 ratio
Base64 encodes every 3 bytes (24 bits) of input into 4 characters. When the input length is not a multiple of 3, the last group is incomplete and padding fills the gap.
entréeHi (2 bytes)输出SGk= -
2. Count the padding characters
If the input length mod 3 equals 1, two padding characters are added. If it equals 2, one padding character is added. If it equals 0, no padding is needed.
entréeA (1 byte) → 2 padding输出QQ== -
3. Decide whether to strip padding
In URL-safe or space-constrained contexts (like JWTs), padding can be stripped because the decoder can infer it from the string length. In standard contexts, keep it for maximum compatibility.
entréeQQ==输出QQ (stripped, URL-safe)
Résultat attendu
You peut predict le nombre de padding caractères de le entrée longueur et safely strip ou restore them quand needed.
Erreurs courantes
- Stripping padding breaks a strict decoder
- Only strip padding when the decoder supports lenient mode or can infer padding from length. Restore padding before passing to strict decoders.
Dépannage指引
- If a decoder rejects a stripped string, re-add = until the length is a multiple of 4.
- Never mix padded and unpadded Base64 in the same data stream.
Limites de sécurité
- Padding carries no security meaning. It is purely structural.