2 commits

Author	SHA1	Message	Date
Kevin Corcoran	95a88286ce	(TK-145) fix default charset in Java client ... Fix a bug in which a default charset of UTF-8 would be added to the Content-Type header for certain requests. This change restricts that behavior to cases in which the body is a string and there is no charset provided by the caller.	2015-02-13 11:32:04 -08:00
Chris Price	88a6e83d48	(PE-5567) Fix bug if content-type header has no charset ... Prior to this commit, the Java client API would throw an NPE if it got a response from a server where the Content-Type header did not include a charset.	2014-08-22 08:03:36 -07:00