Summary: | Result tree : "Response Data" panel is empty on SOAP/XML-RPC sampler | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | David Langlais <david.langlais.fr> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | regression | CC: | greendot, jborgers, yherasym |
Priority: | P2 | ||
Version: | 2.3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP |
Description
David Langlais
2007-12-03 04:44:03 UTC
What does the Sampler Result pane show for the Content-Type under Response Headers? Unless the type is recognised as a text type, it won't be displayable as text. (In reply to comment #1) > What does the Sampler Result pane show for the Content-Type under Response > Headers? > > Unless the type is recognised as a text type, it won't be displayable as text. It looks like this : Response headers: HTTP/1.1 200 OK Date: Mon, 03 Dec 2007 14:31:42 GMT Server: Apache/2.0.49 (Unix) Content-Length: 3176 Connection: close Content-Type: application/soap+xml (SOAP messages are tagged with 'application/soap+xml' in accordance to W3C's recommandations http://www.w3.org/TR/2007/REC-soap12-part2-20070427/#httpmediatype) Try adding the following JMeter property: content-type_text=application/soap+xml to jmeter.properties or user.properties (or on the command-line) I've added application/soap+xml as a text type in SVN r600573 I got application/xml type returned and encountered the same problem in version 3.2.1. It worked flawlessly in 3.2. Please also add application/xml. (In reply to comment #5) > I got application/xml type returned and encountered the same problem in version > 3.2.1. It worked flawlessly in 3.2. Please also add application/xml. Fixed in r610461 *** Bug 44273 has been marked as a duplicate of this bug. *** The change in 2.3.1 has caused quite a few problems, so the next release of JMeter will revert to the previous behaviour. *** Bug 44552 has been marked as a duplicate of this bug. *** *** Bug 44852 has been marked as a duplicate of this bug. *** (In reply to comment #10) > *** Bug 44852 has been marked as a duplicate of this bug. *** > That was incorrect; Bug 44852 is not a duplicate. This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2050 |