You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2003/05/23 14:09:36 UTC
DO NOT REPLY [Bug 20181] New: -
Webservice that require text/xml encoding doesn't work correctly
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20181>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20181
Webservice that require text/xml encoding doesn't work correctly
Summary: Webservice that require text/xml encoding doesn't work
correctly
Product: JMeter
Version: 1.8.1
Platform: All
OS/Version: Other
Status: NEW
Severity: Blocker
Priority: Other
Component: HTTP
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: woolfel@yahoo.com
This bug is related to another soap bug already reported
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8961. I'm trying to use
JMeter to test a ASPX web service. What happens is the server responds "Server
found content type to be 'application/x-www-form-urlencoded', but expected
'text/xml'". The request has to be sent with text/xml encoding since that's what
ASPX webservice demands. I did a little testing with JWSDP and javax.xml.soap
works fine with IIS. the better way to handle webservice soap requests would be
to load the parameters from the WSDL. I'm still trying to find a simple solution
to this that doesn't requiring writing a whole new HTTP sampler and all the
necessary gui elements. Additional information. I use HTTP Header Manager to add
"Content-type: text/xml" and "SOAPAction: <the-url>".
peter lin
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org