Post Content-Type header with specified charset not properly handled

Sometimes, we can have not only "application/x-www-form-urlencoded" on request ContentType.
Example : 'application/x-www-form-urlencoded; charset : UTF-8'