This repository has been archived by the owner on Mar 3, 2022. It is now read-only.

Recommend encoding type #22

Open

philipashlock opened this issue May 2, 2013 · 0 comments

Contributor

philipashlock commented May 2, 2013

I would suggest UTF-8 and this should be specified in the HTTP Content-Type header as well, eg for json the full header would be

Content-Type: application/json; charset=utf-8

See http://utf8everywhere.org/ for some arguments for UTF-8 and arguments against other encodings like UTF-16

konklone mentioned this issue

Use UTF-8 encoding in mime type 18F/api-standards#15

Closed

toolness mentioned this issue

Justify use of charset parameter in JSON payloads 18F/api-standards#68

Closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.