Gregory's Server@neauoire I don't see the handling of the padding and the alternate MME table for base64 url encoding (that has become a silent de facto norm because of sending binary other HTTP GET :D )
|
3 comments
@neauoire Well RFC pedantic might point out that all = in excess MAY be ignored (which decoders often accept (but not always)). I often add "===" after a b64encoded string when I am in the mood for seeing the world burn. And it's fun. I am not convinced by the rationale of the mandatory padding in the RFC in the first place to be honest.  @LaFoulqueDuVexin I think the padding may come in handy when there is no way to detect the end of stream. |
@LaFoulqueDuVexin I was wondering about the padding, I'm writing a decoder, and I don't see the point of it, is it really needed? You can infer the padding based on the queue length.