Remove base64 padding

[alloy]

Consider the following example:

$ curl -Is http://link.artsy.net/click/9692723.214027/aHR0cHM6Ly93d3cuYXJ0c3kubmV0L3ZlbmljZS1iaWVubmFsZS9zdHVkaW8tdmVuZXppYT91dG1fc291cmNlPXNhaWx0aHJ1JnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPTk2OTI3MjMtMDUtMjUtMTctRWRpdG9yaWFsJnV0bV90ZXJtPUFydHN5RmVhdHVyZWRTdG9yaWVz/56d8ca89e9a8a2c4168b4f56Cfbb99b59 | grep Location

Location: https://www.artsy.net/venice-biennale/studio-venezia?utm_source=sailthru&utm_medium=email&utm_campaign=9692723-05-25-17-Editorial&utm_term=ArtsyFeaturedStories

The encoded pattern we have for this is L3ZlbmljZS1iaWVubmFsZQ==, which is not present in the encoded URL. That’s because Base64 encodes in chunks of 3 input bytes and pads the remainder, which means that if the unencoded pattern isn’t exactly a multiple of 3 characters long:

• the trailing = signs will be included, which will not be present in the encoded URL
• the last characters get encoded with the characters following

So instead of encoding /venice-biennale as L3ZlbmljZS1iaWVubmFsZQ==, or even L3ZlbmljZS1iaWVubmFsZQ, we only encode /venice-biennale to L3ZlbmljZS1iaWVubmFs which is present in the encoded URL.

[kanaabe]

Gotcha. Thanks for the explanation and PR. I'll merge and deploy the related apps.

[artsyit]

🚀 PR was released in v1.1.0 🚀