Bug 60424 - Hessian Burlap application : JMeter inserts 0x0D before 0x0A automatically (http binary post data)

Bugzilla Id: 60424

git-svn-id: https://svn.apache.org/repos/asf/jmeter/trunk@1845065 13f79535-47bb-0310-9956-ffa450edef68

Former-commit-id: 498e2bb9e7
This commit is contained in:
Philippe Mouawad 2018-10-28 21:10:03 +00:00
parent 4ac188d4c9
commit 9675f46bf9
4 changed files with 4 additions and 3 deletions

View File

@ -627,7 +627,7 @@ upgrade_properties=/bin/upgrade.properties
# Binary content-type handling
# These content-types will be handled by saving the request in a file:
#proxy.binary.types=application/x-amf,application/x-java-serialized-object
#proxy.binary.types=application/x-amf,application/x-java-serialized-object,binary/octet-stream
# The files will be saved in this directory:
#proxy.binary.directory=user.dir
# The files will be created with this file filesuffix:

View File

@ -63,7 +63,7 @@ public abstract class AbstractSamplerCreator implements SamplerCreator {
static {
String binaries = JMeterUtils.getPropDefault("proxy.binary.types", // $NON-NLS-1$
"application/x-amf,application/x-java-serialized-object"); // $NON-NLS-1$
"application/x-amf,application/x-java-serialized-object,binary/octet-stream"); // $NON-NLS-1$
if (binaries.length() > 0){
StringTokenizer s = new StringTokenizer(binaries,"|, ");// $NON-NLS-1$
while (s.hasMoreTokens()){

View File

@ -135,6 +135,7 @@ Summary
<ul>
<li><bug>62785</bug><pr>400</pr>Incomplete search path applied to the filenames used in the upload functionality of the HTTP sampler. Implemented by Artem Fedorov (artem.fedorov at blazemeter.com) and contributed by BlazeMeter.</li>
<li><bug>62842</bug>HTTP(S) Test Script Recorder : Brotli compression is not supported leading to "Content Encoding Error"</li>
<li><bug>60424</bug>Hessian Burlap application : JMeter inserts 0x0D before 0x0A automatically (http binary post data)</li>
</ul>
<h3>Other Samplers</h3>

View File

@ -796,7 +796,7 @@ JMETER-SERVER</source>
<property name="proxy.binary.types">
Binary <code>content-type</code> handling.<br/>
These <code>content-types</code> will be handled by saving the request in a file.<br/>
Defaults to: <code>application/x-amf,application/x-java-serialized-object</code>
Defaults to: <code>application/x-amf,application/x-java-serialized-object,binary/octet-stream</code>
</property>
<property name="proxy.binary.directory">
The files will be saved in this directory.<br/>