Currently the Web API does not understand Accept-Charset headers where a preference is stated. A value of:
Accept-Charset: utf-16
works, but a value of:
Accept-Charset: utf-8; q=0.2, utf-16;q=1.8
does not. Also, if an unsupported charset is requested, the server should respond with HTTP 406 Not Acceptable. Instead it returns UTF8.
Comments: Having said that... I can't see the Accept-Charset 406 issue any where else. The other mentions of 406 appear to be for different scenarios.
Accept-Charset: utf-16
works, but a value of:
Accept-Charset: utf-8; q=0.2, utf-16;q=1.8
does not. Also, if an unsupported charset is requested, the server should respond with HTTP 406 Not Acceptable. Instead it returns UTF8.
Comments: Having said that... I can't see the Accept-Charset 406 issue any where else. The other mentions of 406 appear to be for different scenarios.