JSON encoding not specified

[KQD]

Regarding a potential fix for 18F/analytics.usa.gov/issues/149, it looks like app/routes.js isn't specifying the character set for the returned JSON. Pulled from StackOverflow #16268244:

Set the res.header("Content-Type", "application/json; charset=utf-8"); so that the browser knows what character set to use.

[CM Lubinski]

+1 this solution. The file command thinks the output is UTF-8 encoded, and vim (being utf-8 aware) displays the characters correctly

[Eric Mill]

The dashboard gets JSON from S3 - the Express endpoints here are not currently used in production. This is a good note and we'll integrate the fix, but it won't resolve 18F/analytics.usa.gov#149.

[Shawn Allen]

Won't S3 let you set the Content-Type header to include the encoding?

[KQD]

@shawnbot It looks like the content encoding is getting set to gzip?

https://github.com/18F/analytics-reporter/blob/master/bin/analytics#L42-L49

[Eric Mill]

We should update the Content-Type, not the Content-Encoding. Thanks for pointing this out -- we'll fix.

[Shawn Allen]

Yeah sorry, I meant that the Content-Type header should be set to application/json; charset=utf-8 on S3, rather than just application/json.

[Susan Tan]

Was this what you had in mind? #128

[Gray Brooks]

@jmhooper, @laurenancona, anyone else here - game to check if #128 resolved this issue?

[Jonathan Hooper]

@gbinal: I believe it would have, but that is dead code now.