I'm trying to use the serverless image handler in our work environment but it doesn't seem to provide any cache mechanism.

The solution is either pass along the Cache headers from S3 (we didn't set any when initially uploading the files). We could update the S3 meta data, or we could pass in the headers we want into the base64 string. This allows for much more customisation. Cache Control, Content Type headers.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.