search

SenorPez / glowing-potato

Trident Support and Tools
http://trident.senorpez.com
MIT License
1 stars 0 forks source link

Sending Alternate Charset Doesn't Fail #24

Closed SenorPez closed 5 years ago

SenorPez commented 5 years ago

Sending "Accept: application/vnd.senorpez.trident.v1+json;charset=UTF-32" returns "Content-Type: application/vnd.senorpez.trident.v1+json;charset=UTF-32". As long as it's a valid charset, this is true.

I'm not sure if the content is actually UTF-32 encoded. I don't think it is, but the API should force UTF-8 headers and responses.

SenorPez commented 5 years ago

Sending those alternate character sets does indeed return the response in the requested character set.

After some consideration, these won't be forced to UTF-8, to allow for local encoding.