On 25.05.20 23:17, Iuri de Araujo Sampaio wrote:
On May 25, 2020, at 08:55, Gustaf Neumann <[email protected]
<mailto:[email protected]>> wrote:
NaviServer has native support for base64 and base64url encoding/decoding
See:
https://naviserver.sourceforge.io/n/naviserver/files/ns_base64.html
Okay, and what about the wring encrypt, (i.e. within “=“) after the
63rd char?
Iuri,
i think, you have mixed something up, and/or you did not read the man page.
Look into the examplein this page: The "base64url" variant performs no
padding
with equal signs. If you have the padding, and you do not want it, use
the right command.
- to use classical base64 encoding (RFC 2045, RFC 4648 sect 4) use,
ns_base64encode/decode.
. to use the base64 encoding with the filename safe alphabet (RFC 4648
sect 5) use,
ns_base64urlencode/decode.
There is now problem with longer strings.
all the best
-gn
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
