[Feature Request]: padded base64 encoder

[rramthun]

What would you like to happen?

Hop's calculator component has an option to encode data as base64.

In theory this allows to use this function to create HTTP basic authentication data for the rest client, e.g. (CSV file with unencoded username:password data) -> (calculator with base64 encoding) -> (REST client using http basic auth with encoded username:password)

In practice this does not work, as the base64 encoder in the calculator uses the un-padded version of base64, but padding is required by the usual HTTP RFCs.

I suggest to add a padded base64 encoder to the calculator transform and will supply a PR for this.

Issue Priority

Priority: 3

Issue Component

Component: Transforms