Bug 52491 - Incorrect parsing of Post data parameters in Tree Listener / Http Request view
Incorrect parsing of Post data parameters in Tree Listener / Http Request view
Status: RESOLVED FIXED
Product: JMeter
Classification: Unclassified
Component: Main
2.5.1
PC All
: P2 normal (vote)
: ---
Assigned To: JMeter issues mailing list
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2012-01-20 15:58 UTC by Liz Gold
Modified: 2012-01-25 16:11 UTC (History)
1 user (show)



Attachments
Screenshot of the HTTP request view on the View Results Tree (175.42 KB, image/pjpeg)
2012-01-20 15:58 UTC, Liz Gold
Details
As requested a sampler file as generated by the http proxy recorder - viewstates and ids are different from my other examples as I have recorded a number of times! Still get the same problem. (4.61 KB, text/plain)
2012-01-20 16:21 UTC, Liz Gold
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Liz Gold 2012-01-20 15:58:17 UTC
Created attachment 28180 [details]
Screenshot of the HTTP request view on the View Results Tree

I'm trying to test Seam Remoting UI as part of my performance testing using JMeter.

I can get to the page, I then click to return some data to the ui via seam remoting and it seems the replay of the HTTP Request is broken, in the sense when I click on the http request of the View Results tree and then look at the Request in HTTP view the original request parameter value has been broken up haphazardly into partly:
- parameter name: <envelope><header><context><conversationId>234</conversationId></context></header><body><call component
- value: "OrderTransfer" method 
- and some lost altogether: ="getTemplateString" id="0"> <params></params><refs></refs></call></body></envelope>

original value: <envelope><header><context><conversationId>234</conversationId></context></header><body><call component="OrderTransfer" method="getTemplateString" id="0"> <params></params><refs></refs></call></body></envelope>

The Http Request is that generated directly by the JMetter recording tool using the Http Proxy. I have soley replaced the viewstate and page id variables to map what they should be (using variables that are all correctly set at runtime). According to the JMeter component help documentation this is (having a HTTP POST request parameter with blank name and a value) correct if we wish to replace the request body with the above (envelope xml). At present the request returns nothing (is not working) whereas on our real server (when not proxy recording / test running) we get a response back for this request.
Comment 1 Sebb 2012-01-20 16:03:41 UTC
Please attach the sampler as generated by the JMeter proxy.

Select the sampler and use Save As to create a file; redact any sensitive information before attaching the file.
Comment 2 Liz Gold 2012-01-20 16:21:38 UTC
Created attachment 28181 [details]
As requested a sampler file as generated by the http proxy recorder - viewstates and ids are different from my other examples as I have recorded a number of times! Still get the same problem.
Comment 3 Sebb 2012-01-20 17:46:37 UTC
As far as I can tell, the data that is sent is correct - have a look in the Raw Request view - does that look OK?

It seems that the conversion to HTTP view is incorrect, but that is a display-only fault. 

It should probably not attempt to parse POST bodies unless they really do look like name=value parameters
Comment 4 Liz Gold 2012-01-23 10:17:32 UTC
The data in the raw Request view is correct. So this does seem like a GUI issue on the Http Request view.
Comment 5 Sebb 2012-01-25 16:11:49 UTC
URL: http://svn.apache.org/viewvc?rev=1235804&view=rev
Log:
Bug 52491 - Incorrect parsing of Post data parameters in Tree Listener / Http Request view

Modified:
   jmeter/trunk/src/protocol/http/org/apache/jmeter/protocol/http/visualizers/RequestViewHTTP.java
   jmeter/trunk/xdocs/changes.xml