Change media_type of JSONResponse to "application/json; charset=utf-8" about starlette

[Kludex]

MRE: #2340 (reply in thread)

[Kludex]

And when I change media_type of JSONResponse to "application/json; charset=utf-8", this issue solved

This is not true. The charset set doesn't solve anything.

[neolooong]

From muxacarin provided sample code, the two endpoints have different response just because of calling json.dumps without pass ensure_ascii=False.

And when I change media_type of JSONResponse to "application/json; charset=utf-8", this issue solved.

Adding charset=utf-8 is not intended to make both endpoints respond the same.

The problem is if starlette do not provide charset=utf-8 explicitly, some client cannot parse response correctly. dart http library is the one. It would use latin1, if charset is unknown.

[Kludex]

From muxacarin provided sample code, the two endpoints have different response just because of calling json.dumps without pass ensure_ascii=False.

And when I change media_type of JSONResponse to "application/json; charset=utf-8", this issue solved.

Adding charset=utf-8 is not intended to make both endpoints respond the same.

The problem is if starlette do not provide charset=utf-8 explicitly, some client cannot parse response correctly. dart http library is the one. It would use latin1, if charset is unknown.

Ah. Got it!

I've been reading around, and I understand why we don't send the chatset=utf-8 on application/json. The reason is that JSON already assumes UTF-8: https://datatracker.ietf.org/doc/html/rfc4627#section-3.

Since that's the case, I think HTTP clients that don't make this consideration should be in the wrong.

Thanks for the help here.