Force UTF-8 charset on JSON responses

[franzliedke]

As suggested in this forum topic, I made sure JSON responses are always sent explicitly as UTF-8 (which fixes a display bug).

The RFC says that JSON "SHOULD" be sent as UTF-8, so that makes sense.

[franzliedke]

Meh.

Signed-off-by: Franz Liedke franz@develophp.org

[darrenpowers]

I have not used jsonp much and may be miss understanding it or laravel or even the http rfc but should we not be using Config::get('application.encoding') rather than hard coding UTF-8?
What if the response needed to be in UTF-16?

[franzliedke]

Citing from the aforementioned forum topic:

RFC4627 states that "JSON text SHALL be encoded in Unicode. The default encoding is UTF-8."

[darrenpowers]

Ok I get that but what if a user set their applications default to UTF-16 (still unicode) and didn't pass a charset to in the header or no header at all as is common practice with json responses. The user might expect their application default to be used just like it is elsewhere. I assume in the aforementioned RFC the default of UTF-8 should only be used if no other valid option was given and I would assume a quick check of the applications encoding would be better than dropping all the way back to one default.