Yes. It is indeed sent through the network in a compressed format and presented to you in a readable form in jmeter. And it is presented to you that way because, only deflated files can help you implement content checks and correlations in your scripts.
As you said the server has responded to your request with a gzip token in the accept-encoding field, a meta-data declaration has been made by the server and it can seldom be false. So, I guess, now you should be convinced. -Chaitanya M Bhatt http://www.performancecompetence.com On Mon, Aug 9, 2010 at 4:20 AM, balaji <[email protected]> wrote: > > Thanks Chaitanya, but when i use "Accept-encoding: gzip, deflate" in xml > version tag, I get response as XML document invalid. > > However when I omit the encoding attribute itself I still see the below > with > or without encoding attribute specfied in my Soap Request > > Response Http headers > Accept-Encoding: gzip,deflate > > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > > > These are seen in the response Http headers tracked through Live Http > Headers plug-in in Firefox Browser. > > Also as you said earlier, could you please confirm that my response is > always decompressed implicity and presented in the readable format in > Jmeter > > > Thanks > Balaji > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/How-to-view-SOAP-Response-in-gZip-Compressed-format-tp2268583p2268651.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
