DO NOT REPLY [Bug 48372] New: multibyte data getting corrupted with HTTP POST - when used JMeter 2.3.4

[email protected]
Newsgroups gmane.comp.jakarta.jmeter.devel
Message-ID <[email protected]/bugzilla/>
https://issues.apache.org/bugzilla/show_bug.cgi?id=48372

           Summary: multibyte data getting corrupted with HTTP POST - when
                    used JMeter 2.3.4
           Product: JMeter
           Version: 2.3.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: HTTP
        AssignedTo: [email protected]
        ReportedBy: [email protected]


Created an attachment (id=24689)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=24689)
contains 2 png image files showing the execution with jmeter 2.3.4 and 2.3RC4 

I had initially created a testplan using JMeter 2.3RC4  - because this was
available as latest when i started using Jmeter for my work. All things were
working absolutely fine on this.

About 2 days back i wanted to pick the latest available version of Jmeter and
start using it . Hence i downloaded 2.3.4 official release version.  

so, opened my existing jmx testplan file using 2.3.4  & executed/run the
testcase.


PROBLEM:
the multibyte data for the HTTP POST requests are getting garbled.
i.e
> if i run the same using 2.3RC4 - everything works fine - multibyte data is handled correctly.
> if i open same jmx file using 2.3.4  & run it  - multibyte data becomes garbled .


ATTACHMENTS: 
I have attached screen shots(two .png images are zipped): shows same testcase
run on 2.3RC4 and 2.3.4 . If you notice in that pictures -  on 2.3RC4 the
result is fine and multibyte data is also correct.  on 2.3.4 , the multibyte
data is corrupted.



DETAILS:

The HTTP Request was created as follows :

>  Test Plan->Add->Thread Group. Entered the name and other fields.
>  Again Right Clicked on ThreadGroup->Add->Sampler->HTTP Request.
>  there i choose METHOD = POST .  [in some tests we need multi-part , in some
>  we need only POST]
>  Entered the name of the request and the Path/command . Typed UTF-8 in Content
>  Encoding textbox.
>  This is how that HTTP POST request is filled up.
>

Also in jmeter.properties file  :  i have given :
sampleresult.default.encoding  = UTF-8


When i run the testcases , the response assertion checks for a particular
multibyte content in the http response received.  It fails because , i can see
the HTTP Response  under View result tree  - which has been garbled.

The same testcase when run using 2.3RC4 works absolutely fine and testcase
passes. There is absolutely no change b/w the way i run in 2.3.RC4 & 2.3.4 .  
With 2.3.4 it fails because multibyte content is getting corrupted.


NOTE:
The HTTP GET request handles the multibyte data correctly .The garbling issue
is noticed only when i have HTTP POST.


Additional observation :
(in case if its relevant)
On 2.3.4 ,  After running the testcase . go to  View Result Tree , there is a
node called "Sample Result". Under this the following entries are noticed for
POST request:

   HTTPSampleResult fields:
   DataEncoding: ISO-8859-1

Now. If i change the HTTP request method to GET , the above is seen as follows:

   HTTPSampleResult fields:
   DataEncoding: utf-8


So - what is impacting this i do not know.  



ISSUE MARKED AS BLOCKER :
The issue iam raising as blocker because , all HTTP POST request's multibyte
content is getting garbled if i use 2.3.4 .  Basically i cannot use 2.3.4 for
running my tests having HTTP POST.

As workaround :  
iam just using the previous version that we had picked - 2.3RC4 itself. With
2.3.RC4 everything works absolutely fine.


Kindly fix the problem for 2.3.4.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.