I saw it had collapsed non-ascii characters originally encoded in utf-8.
For example, for ブーツ it produced ãã¼ã.
It'd be favorable to respect Content-Type in the response header.
Also, it'd be nice to pass the original base64 encoded data to event handlers that will bring a chance to solve this kind of problem by them.
I saw it had collapsed non-ascii characters originally encoded in utf-8.
For example, for
ブーツit producedãã¼ã.It'd be favorable to respect
Content-Typein the response header. Also, it'd be nice to pass the original base64 encoded data to event handlers that will bring a chance to solve this kind of problem by them.