added utf-8 support.

[chrisamti]

No description provided.

[adrianrudnik]

Hi @chrisamti thanks for the PR!

Out of curiosity, what arm64 devices do you use?

Do you see any reason to split CHARSET and DEFAULT_RESPONSE_CONTENT_TYPE or could it be text/html; charset=${CHARSET}"?

[chrisamti]

AWS ARM64 and Apple Silicon M1.

Do you see any reason to split CHARSET and DEFAULT_RESPONSE_CONTENT_TYPE or could it be text/html; charset=${CHARSET}"?

Maybe. Did not test that. As far as I know the http header is only valid if written as:

Content-Type: text/html; charset=utf-8

I assume

Content-Type: text/html; charset=utf8

is not valid.

and

res.write(result.html, charsetOpts.write)

https://nodejs.org/api/http.html#http_request_write_chunk_encoding_callback

requires utf8

So I decided to have 2 ENV vars.