You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2019/07/02 11:05:22 UTC

[Bug 63536] New: JMeter support for vars.putObject binary post data and gzip post data

https://bz.apache.org/bugzilla/show_bug.cgi?id=63536

            Bug ID: 63536
           Summary: JMeter support for vars.putObject binary post data and
                    gzip post data
           Product: JMeter
           Version: 5.1.1
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTTP
          Assignee: issues@jmeter.apache.org
          Reporter: liu_xp2003@sina.com
  Target Milestone: JMETER_5.2

Could JMeter support binary post data for following two cases
1. when using vars.putObject function to set arrary object data.
2. when using "Content-Encoding: gzip" in post request header the request body
data could be compressed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 63536] JMeter support for vars.putObject binary post data and gzip post data

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63536

Liu XP <li...@sina.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #2 from Liu XP <li...@sina.com> ---
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.

[Bug 63536] JMeter support for vars.putObject binary post data and gzip post data

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63536

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
(In reply to Liu XP from comment #0)
> Could JMeter support binary post data for following two cases
> 1. when using vars.putObject function to set array object data.

I am not sure to understand, can you clarify what is currently not possible ?


> 2. when using "Content-Encoding: gzip" in post request header the request
> body data could be compressed

This duplicates Bug 58609

-- 
You are receiving this mail because:
You are the assignee for the bug.