https://bz.apache.org/bugzilla/show_bug.cgi?id=63536
Liu XP <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW --- Comment #2 from Liu XP <[email protected]> --- For example: The implementation source code of HTTP Client 4 in current master branch jmeter\src\protocol\http\org\apache\jmeter\protocol\http\sampler\HTTPHC4Impl.java The line 1587 below shows that all the post data will be converted to StringEntity first. Thus, the original post data format couldn't be used, such as ProtoBuff Msg. StringEntity requestEntity = new StringEntity(postBody.toString(), contentEncoding); For question 1: I hope JMeter could support original post data format when the request included special content-type. Because there is no judging condition about request content-encoding, all request will not be compressed. For question 2: I think following entity could be used to support gzipCompress. HttpEntity entity = EntityBuilder.create().setText(postBody.toString()).gzipCompress().setContentEncoding(contentEncoding).build(); -- You are receiving this mail because: You are the assignee for the bug.
