On 09/12/2009, jmltest jmltest <[email protected]> wrote: > Just wanted to inform : > i have set this field called : > > sampleresult.default.encoding = UTF-8 > > basically the properties files of jmeter have same settings as i used in > 2.3RC4 . The above one was was important and hence wanted to inform that > everything is taken care exactly same way as done with 2.3RC4. > > so can you kindly help me - what is the problem with HTTP POST requests > containing multibyte data - which is going garbled. > > Also one problem i noticed :
This is nothing to do with the original query. > when i go to view result tree . and see under the Sample Result node , > there the following entry is shown : > > HTTPSampleResult fields: > > DataEncoding: ISO-8859-1 > > > how did this come into picture ? what is the impact of this . ? i do not see > this on older versions . What does this mean - i do not know. Kindly > explain to me. This just means that the Listener now shows the value of the DataEncoding field. > does 2.3.4 has any changes/bugs that has impacted POST requests handling > multibyte data. Which HTTP Sampler are you using? HttpClient or the default? > Also FYI : GET requests with multibyte data on 2.3.4 works fine. The problem > is only with POST requests. Please create a Bugzilla issue, and attach the smallest possible test plan that shows the problem - i.e. just include the HTTP POST sampler. > thanks > jml > > > On Wed, Dec 9, 2009 at 3:23 PM, jmltest jmltest > <[email protected]>wrote: > > > > Hi Jmeter Team, > > > > I have a problem with POST when moved to latest 2.3.4 version of Jmeter. > > Below is my scenario explained : > > > > > > when i started writing the testplan using Jmeter - i had downloaded the > > version = 2.3RC4. > > The HTTP POST requests , were working fine . i.e multibyte data was > > working fine for my requests/responses. Everything with this jmeter version > > absolutely works fine w.r.t multibyte data. Note: Earlier to this version > > the content was getting corrupted. We saw some bug fixes being mentioned. > > Hence we picked this 2.3RC4 which was latest available at that time . > > > > > > Now, about 2 days back i wanted to use latest Jmeter version . So i > > downloaded latest released version i.e 2.3.4 . > > Then , > > Opened my existing .jmx file having my testcases/plan. > > then Ran/executed that test - i.e HTTP POST request using this jmeter > > version. > > > > Problem : > > > > the data is getting corrupted & POST request fails (because my response > > assertion is checking for a multibyte data content in the Response data > > obtained ) . I can see under the view result tree that the Responses are > > having multibyte data getting corrupted - its garbled. > > > > > > Please Note: > > In my HTTP Requests , i have set the Content Encoding to UTF-8 . Also > > there has been absolutely no change when i opened my same jmx file in new > > jmeter gui. i.e > > > > --- If i run my .jmx file in 2.3RC4 version , it works fine properly > > ---- if i run the same jmx file using 2.3.4 version , it fails. i.e > > multibyte data gets corrupted . > > > > > > Note: jmeter.properties file has settings also same . No change as such b/w > > the versions when i ran the jmeter. > > > > Could you please tell me if anything changed in 2.3.4 that caused this > > problem --- does HTTP POST requests containing Multibyte data work with > > 2.3.4 ? is there anything extra that i need to do here ? > > Why the same testcase runs successfully in 2.3.RC4 , but fails when i > > execute same on 2.3.4 ? > > > > > > can you kindly help me . > > > > thanks > > jml. > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
