JMeter currently follows the RFCs and creates multi-part headers of the form: -----------------------------7d159c1302d0y0 Content-Disposition: form-data; name="PARAM" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit However, many browse only provide the following: -----------------------------7d159c1302d0y0 Content-Disposition: form-data; name="PARAM" Further, some broken servers reject the valid Content-Type and CTE headers. It would be useful to be able to optionally operate Multipart Posts in browser-compatible mode.
Implemented and added to SVN: URL: http://svn.apache.org/viewvc?rev=1064940&view=rev Log: Bug 50684 - Optionally disable Content-Type and Transfer-Encoding in Multipart POST Modified: jakarta/jmeter/trunk/docs/images/screenshots/http-request.png jakarta/jmeter/trunk/src/core/org/apache/jmeter/resources/messages.properties jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/config/gui/UrlConfigGui.java jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPAbstractImpl.java jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC3Impl.java jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPHC4Impl.java jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/HTTPSamplerBase.java jakarta/jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/sampler/PostWriter.java jakarta/jmeter/trunk/xdocs/changes.xml jakarta/jmeter/trunk/xdocs/images/screenshots/http-request.png jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml This will be in nightly builds from 1064940
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2462