On Mon, May 28, 2018 at 03:10:01PM +0100, Jonathan Matthews wrote: > On Mon, 28 May 2018 at 14:26, Willy Tarreau <w...@1wt.eu> wrote: > > > On Mon, May 28, 2018 at 01:43:41PM +0100, Jonathan Matthews wrote: > > > Improvements and suggestions welcome; flames and horror -> /dev/null ;-) > > > > Would anyone be interested in adding two new converters for this, > > working exactly like base64/b64dec but with the URL-compatible > > base64 encoding instead ? We could call them : > > > > u64dec > > u64enc > > > I like that idea, and have already retrieved my K&R from the loft :-)
By the way, another approach (cleaner?) could be to add an argument to the existing b64dec()/base64() to indicate how it should work. I think it's the utf8 or json or something like this which already does exactly this. Willy
