Base64 padding mismatch

[delaneyj]

I have a situation where I'm trying to pull down data from an object store put there by a Go client. Pulling this data from the cli with --trace shows the underlying metadata being called on $O.web-friendly-images.M.MTIyMDE5NTQ0MDYwMzY5MDA2NjJfMDAwMTlfZnVsbA== however the same object being pulled from JS shows up as $O.web-friendly-images.M.MTIyMDE5NTQ0MDYwMzY5MDA2NjJfMDAwMDFfZnVsbA.

This leads the js clients to see this as a 404 even though the data is available in the CLI. It appears there is a discrepancy between clients in how padding of base64 is handled. I couldn't find any documentation on which client is "right" though I assume the Go one is the closest to a reference implementation.

If you need more details please don't hesitate to ask.