v0.4.3

• Fixed a bug when the response was a UTF-8 encoded text/html body, but the content-type header didn't explicitly specify it (text/html instead of text/html; charset=utf8). In that case the Lambda response object had isBase64Encoded set to false and the body was a base64 encoded string. Api Gateway REST API ignores the isBase64Encoded flag when the content-type is text-html and doesn't decode the base-64 body but returns it back to the user.