ParentFull threadenan·Thanks, fixed! The content-type header was missing the encoding on the S3 object!View on HN