| Subject: | Serializer does not set charset in Content-Type header |
SerializeBase.pm, line 134:
$c->response->content_type($content_type);
The content type is straight out of the mapping hash, and so no charset
parameter is appended. The HTTP default is ISO 8859-1 rather than UTF-8.
If you are working with UTF-8 data (e.g. serialized JSON), this is not good.
I don't know if you want to hard-code append "; charset=utf-8", or make
it configurable, or leave the decision to the serializer, but there
needs to be some way of making this work :-)
Gerv