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: You are right... I had been just looking at the Accept-Charset header spec that doesn't set an upper bound to q, but I guess it can be inferred from the Accept header spec which does set boundaries. It is good to know the other minor issue is being looked at.
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: You are right... I had been just looking at the Accept-Charset header spec that doesn't set an upper bound to q, but I guess it can be inferred from the Accept header spec which does set boundaries. It is good to know the other minor issue is being looked at.