RE: Suggestion for enhancing 'HTTP Request' sampler
Thanks Peter - I hope to check it out soon and let you know. Adding a textbox to the HTTP sampler instead would leverage the 'Follow-redirects' and other HTTP options that the HTTP sampler provided. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Friday, 16 January 2004 12:53 AM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, I just updated the soap sampler to check the header manager for content- type. Please give it a try and see if that works for you. You may have to build from CVS or wait for the nightly. peter lin Sonam Chauhan [EMAIL PROTECTED] wrote: Thanks a lot Peter - appreciate you looking into this issue. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 January 2004 10:42 AM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler I'll take a look and see if I can make that change. peter lin --- Sonam Chauhan wrote: Kenneth - Thanks for the suggestion. I don't understand it completely, but it probably does not apply to my problem because I am posting non-XML data (specifically, a MIME-format 'CommerceOne envelope'). Peter- Thanks for your suggestion. I had used the HTTP header manager, but the SOAP sampler ignored the content-type setting I set there. I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. I think the SOAP sampler simply hardcodes Content-type to 'text/xml' (stands to reason since it is only meant for XML). The simplest fix would be to add a textbox to the regular HTTP sampler that allows the user to simply paste in the content of the HTTP request body. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 January 2004 2:03 AM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, did you try adding a http config element to set the content-type? add - config element - http header manager. that might work. can you give it a try and see if that fixes it? peter lin Sonam Chauhan wrote: that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. ... if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. Hi Peter - The SOAP sampler presents a different Content-type HTTP header which may be causing the problem. Here are the HTTP request headers used by the CommerceOne application: -- Accept=image/gif, */* Authorization=Basic xxx== Content-Length=11345 Content-type=application/x-www-form-urlencoded Host=internal_server:80 marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Mozilla/4.0 [en] (WinNT; I) -- Here are the HTTP request headers used by the JMeter SOAP/XML sampler. -- Accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection=close Content-length=6782 Content-type=text/xml Host=internal_server marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Java/1.4.2_02 -- I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. The strange thing is that HTTP request body seemed empty when the JMeter SOAP sampler presented it. However, this could be a glitch in my CGI rather than with the SOAP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 January 2004 2:54 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler that makes sense. but back
RE: Suggestion for enhancing 'HTTP Request' sampler
Sonam, Peter,
If you are interested - after a quick look, this issue appears to be
very similar to the problem I had with doing XMLHTTP posts to the server
from the MS XMLHTTP control - that control sends the http post as
straight XML and the HTTP request handler would try to parse it out into
parameters (see parseArguments())- I primarily patched HTTPSampler,
HTTPArgument, and PostWriter to handle XML posts differently, so they
could be captured by the proxy, and played back by the script as
non-parameterized post data.
...
if (queryString.startsWith() queryString.endsWith()) {
addArgument(XMLHTTP,queryString,=);
} else {
...
I posted this info on the list about a month ago or so (search for
XMLHTTP) but there seemed to be little/no interest so I just regarded it
as something only I have encountered. Perhaps using this fix which just
captures any XML in a post, and plays it back the same way it is
received might help seeing as how the CommerceOne application appears to
be functioning more like MS XMLHTTP than SOAP.
Just a thought ...
__
Kenneth Chenis
McKesson Health Solutions, LLC
275 Grove Street, Suite 1-110
Newton, MA 02466
v: (617) 273-3057
e: [EMAIL PROTECTED]
-Original Message-
From: Sonam Chauhan [ mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] ]
Sent: Wednesday, January 14, 2004 1:41 AM
To: 'JMeter Developers List'
Subject: RE: Suggestion for enhancing 'HTTP Request' sampler
that makes sense. but back to the task of how can the
soap/xml-rpc sampler can be enhanced to work with
CommerceOne.
...
if you can list exactly what the service needs in
terms of encoding, content-type, content-length, post
and so on, I can take a look.
Hi Peter - The SOAP sampler presents a different Content-type HTTP
header which may be causing the problem.
Here are the HTTP request headers used by the CommerceOne application:
--
Accept=image/gif, */*
Authorization=Basic xxx==
Content-Length=11345
Content-type=application/x-www-form-urlencoded
Host=internal_server:80
marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001
User-Agent=Mozilla/4.0 [en] (WinNT; I)
--
Here are the HTTP request headers used by the JMeter SOAP/XML sampler.
--
Accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection=close
Content-length=6782
Content-type=text/xml
Host=internal_server
marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001
User-Agent=Java/1.4.2_02
--
I used the HTTP header manager to create the special
marketparticipantid=xxx header, but could not override the
Content-type=text/xml header.
The strange thing is that HTTP request body seemed empty when the JMeter
SOAP sampler presented it. However, this could be a glitch in my CGI
rather than with the SOAP sampler.
With regards,
Sonam Chauhan
--
Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED]
___
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended
recipient(s). The information contained in this message may be private
and confidential, and may also be subject
to the work product doctrine. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not
the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message.
RE: Suggestion for enhancing 'HTTP Request' sampler
hi sonam, did you try adding a http config element to set the content-type? add - config element - http header manager. that might work. can you give it a try and see if that fixes it? peter lin Sonam Chauhan [EMAIL PROTECTED] wrote: that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. ... if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. Hi Peter - The SOAP sampler presents a different Content-type HTTP header which may be causing the problem. Here are the HTTP request headers used by the CommerceOne application: -- Accept=image/gif, */* Authorization=Basic xxx== Content-Length=11345 Content-type=application/x-www-form-urlencoded Host=internal_server:80 marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Mozilla/4.0 [en] (WinNT; I) -- Here are the HTTP request headers used by the JMeter SOAP/XML sampler. -- Accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection=close Content-length=6782 Content-type=text/xml Host=internal_server marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Java/1.4.2_02 -- I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. The strange thing is that HTTP request body seemed empty when the JMeter SOAP sampler presented it. However, this could be a glitch in my CGI rather than with the SOAP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 January 2004 2:54 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. What exactly does the service require? From the previous emails I get the impression it's not just a post. If it was just a post, the soap/xml-rpc sampler should work. if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. peter lin --- Sonam Chauhan wrote: Hi Peter - thanks for all your inputs! Sorry man - the commerceone document I included in the message below isn't SOAP, or even XML at all - it's an older, MIME-lookalike type of format used by most CommerceOne Marketsites. I didn't mean to imply that the Webservices sampler or the SOAP/XML-RPC samplers should be able to handle that document - they shouldn't. I was pointing out that no current JMeter sampler could POST that document and an enhancement to the regular HTTP sampler would enable that document, and any other document to be posted by the regular HTTP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes
RE: Suggestion for enhancing 'HTTP Request' sampler
I'll take a look and see if I can make that change. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Kenneth - Thanks for the suggestion. I don't understand it completely, but it probably does not apply to my problem because I am posting non-XML data (specifically, a MIME-format 'CommerceOne envelope'). Peter- Thanks for your suggestion. I had used the HTTP header manager, but the SOAP sampler ignored the content-type setting I set there. I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. I think the SOAP sampler simply hardcodes Content-type to 'text/xml' (stands to reason since it is only meant for XML). The simplest fix would be to add a textbox to the regular HTTP sampler that allows the user to simply paste in the content of the HTTP request body. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 January 2004 2:03 AM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, did you try adding a http config element to set the content-type? add - config element - http header manager. that might work. can you give it a try and see if that fixes it? peter lin Sonam Chauhan [EMAIL PROTECTED] wrote: that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. ... if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. Hi Peter - The SOAP sampler presents a different Content-type HTTP header which may be causing the problem. Here are the HTTP request headers used by the CommerceOne application: -- Accept=image/gif, */* Authorization=Basic xxx== Content-Length=11345 Content-type=application/x-www-form-urlencoded Host=internal_server:80 marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Mozilla/4.0 [en] (WinNT; I) -- Here are the HTTP request headers used by the JMeter SOAP/XML sampler. -- Accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection=close Content-length=6782 Content-type=text/xml Host=internal_server marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Java/1.4.2_02 -- I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. The strange thing is that HTTP request body seemed empty when the JMeter SOAP sampler presented it. However, this could be a glitch in my CGI rather than with the SOAP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 January 2004 2:54 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. What exactly does the service require? From the previous emails I get the impression it's not just a post. If it was just a post, the soap/xml-rpc sampler should work. if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. peter lin --- Sonam Chauhan wrote: Hi Peter - thanks for all your inputs! Sorry man - the commerceone document I included in the message below isn't SOAP, or even XML at all - it's an older, MIME-lookalike type of format used by most CommerceOne Marketsites. I didn't mean to imply that the Webservices sampler or the SOAP/XML-RPC samplers should be able to handle that document - they shouldn't. I was pointing out that no current JMeter sampler could POST that document and an enhancement to the regular HTTP sampler would enable that document, and any other document to be posted by the regular HTTP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http
RE: Suggestion for enhancing 'HTTP Request' sampler
Thanks a lot Peter - appreciate you looking into this issue. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 January 2004 10:42 AM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler I'll take a look and see if I can make that change. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Kenneth - Thanks for the suggestion. I don't understand it completely, but it probably does not apply to my problem because I am posting non-XML data (specifically, a MIME-format 'CommerceOne envelope'). Peter- Thanks for your suggestion. I had used the HTTP header manager, but the SOAP sampler ignored the content-type setting I set there. I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. I think the SOAP sampler simply hardcodes Content-type to 'text/xml' (stands to reason since it is only meant for XML). The simplest fix would be to add a textbox to the regular HTTP sampler that allows the user to simply paste in the content of the HTTP request body. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Thursday, 15 January 2004 2:03 AM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, did you try adding a http config element to set the content-type? add - config element - http header manager. that might work. can you give it a try and see if that fixes it? peter lin Sonam Chauhan [EMAIL PROTECTED] wrote: that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. ... if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. Hi Peter - The SOAP sampler presents a different Content-type HTTP header which may be causing the problem. Here are the HTTP request headers used by the CommerceOne application: -- Accept=image/gif, */* Authorization=Basic xxx== Content-Length=11345 Content-type=application/x-www-form-urlencoded Host=internal_server:80 marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Mozilla/4.0 [en] (WinNT; I) -- Here are the HTTP request headers used by the JMeter SOAP/XML sampler. -- Accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection=close Content-length=6782 Content-type=text/xml Host=internal_server marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Java/1.4.2_02 -- I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. The strange thing is that HTTP request body seemed empty when the JMeter SOAP sampler presented it. However, this could be a glitch in my CGI rather than with the SOAP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 January 2004 2:54 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. What exactly does the service require? From the previous emails I get the impression it's not just a post. If it was just a post, the soap/xml-rpc sampler should work. if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. peter lin --- Sonam Chauhan wrote: Hi Peter - thanks for all your inputs! Sorry man - the commerceone document I included in the message below isn't SOAP, or even XML at all - it's an older, MIME-lookalike type of format used by most CommerceOne Marketsites. I didn't mean to imply that the Webservices sampler or the SOAP/XML-RPC samplers should be able to handle that document
RE: Suggestion for enhancing 'HTTP Request' sampler
the webservice sampler uses apache soap. the soap API requires the message meet soap requirements. the Soap/xml-rpc may be able to handle it. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Hi guys - The main reason I suggested enhancing the HTTP sampler instead was so it can POST complex documents like the one below. It is not a XML document, and the content type is not 'text/xml'. Correct me if I am wrong, but I think none of the current samplers (HTTP, SOAP and webservices samplers) can POST this document: _ Message-ID: [EMAIL PROTECTED] Date: Tue, 13 Jan 2004 13:50:47 +1100 (GMT+11:00) Mime-Version: 1.0 Content-Type: multipart/related; boundary==_Part_187_175861948.1073962247153 Content-ID: c5732f42-78e6-1000-93a0-ac1001760001 x-Date-Sent: 13 Jan 2004 13:50:47 GMT+11:00 referenceId: x-Document-Type: Error ... --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=Error; ns=urn:x- ... Error.../Error --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=catalog; ... !DOCTYPE ... ... _ Peter - Thanks - the Dec 29 CVS didn't have the webservices sampler, but the 1.9.1. stable release has an alpha version of your webservices sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 2:29 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, please take a look at the webservices sampler. It uses Apache soap driver. it can read xml envelope from text area, a file or randomly select files from a directory. it's been tested with .NET webservices. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Well, I may be missing something... (so do correct me.) However, if all that SOAP sampler does is: 1. Set content-type=text/xml 2. POST contents of it's textbox with no parameters ... it would be better to bundle that functionality into the HTTP sampler because: a. The HTTP sampler is more mature (as you said) b. It has more functionality. For e.g.: redirects/keep-alives (though I don't know if these are applicable to XML POSTs) The other point I had was certain HTTP POSTs are impossible - both with the HTTP sampler and the SOAP sampler. For e.g.: the multipart-MIME HTTP posts like the one CommerceOne envelope I mentioned below. If the HTTP sampler could load the actual *body* of the POST from a textbox or a file, then, in combination with the HTTP header manager, it could do anything. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:49 AM To: JMeter Developers List Subject: Re: Suggestion for enhancing 'HTTP Request' sampler Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan ha escrit: The normal HTTP sampler seems incapable of posting XML documents using the process below (it falls down in point #2): 1. The HTTP content-type is set to text/xml. 2. The HTTP request body contains the document itself (no POST parameters are used) However, the 'SOAP/XML-RPC Request' sampler seems to handle this process well. The normal HTTP sampler can be made more generic by allowing it to POST the contents of a file or a textbox *without* POST parameters. In this case, there would be no need of the 'SOAP/XML-RPC Request' sampler - is this correct? Also, the above would make possible certain complex HTTP requests that currently are impossible with JMeter. For e.g.: CommerceOne marketsite envelopes that have multiple content-parts with no POST parameters. With regards, Sonam Chauhan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - === message
RE: Suggestion for enhancing 'HTTP Request' sampler
Thanks Peter. I just tried the SOAP sampler with that document but the receiving server spits out an error - possibly because of 'incorrect' HTTP header used by SOAP sampler (the document isn't really XML). Unfortunately, I can't find out exactly what's wrong since 'View Results Tree' only shows HTTP response headers. Does anyone know offhand of a JMeter debug level that dumps HTTP *request headers* to jmeter.log? (I tried 'jmeter -Ljmeter=DEBUG' but it only dumps the request body, not the request headers.) It would be better if the HTTP sampler added the facility to submit the contents of a textbox or a file. In combination with the HTTP header manager, any kind of HTTP POST would be possible (including the document below - a 'CommerceOne envelope') With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:10 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler the webservice sampler uses apache soap. the soap API requires the message meet soap requirements. the Soap/xml-rpc may be able to handle it. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Hi guys - The main reason I suggested enhancing the HTTP sampler instead was so it can POST complex documents like the one below. It is not a XML document, and the content type is not 'text/xml'. Correct me if I am wrong, but I think none of the current samplers (HTTP, SOAP and webservices samplers) can POST this document: _ Message-ID: [EMAIL PROTECTED] Date: Tue, 13 Jan 2004 13:50:47 +1100 (GMT+11:00) Mime-Version: 1.0 Content-Type: multipart/related; boundary==_Part_187_175861948.1073962247153 Content-ID: c5732f42-78e6-1000-93a0-ac1001760001 x-Date-Sent: 13 Jan 2004 13:50:47 GMT+11:00 referenceId: x-Document-Type: Error ... --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=Error; ns=urn:x- ... Error.../Error --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=catalog; ... !DOCTYPE ... ... _ Peter - Thanks - the Dec 29 CVS didn't have the webservices sampler, but the 1.9.1. stable release has an alpha version of your webservices sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 2:29 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, please take a look at the webservices sampler. It uses Apache soap driver. it can read xml envelope from text area, a file or randomly select files from a directory. it's been tested with .NET webservices. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Well, I may be missing something... (so do correct me.) However, if all that SOAP sampler does is: 1. Set content-type=text/xml 2. POST contents of it's textbox with no parameters ... it would be better to bundle that functionality into the HTTP sampler because: a. The HTTP sampler is more mature (as you said) b. It has more functionality. For e.g.: redirects/keep-alives (though I don't know if these are applicable to XML POSTs) The other point I had was certain HTTP POSTs are impossible - both with the HTTP sampler and the SOAP sampler. For e.g.: the multipart-MIME HTTP posts like the one CommerceOne envelope I mentioned below. If the HTTP sampler could load the actual *body* of the POST from a textbox or a file, then, in combination with the HTTP header manager, it could do anything. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:49 AM To: JMeter Developers List Subject: Re: Suggestion for enhancing 'HTTP Request' sampler Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan
RE: Suggestion for enhancing 'HTTP Request' sampler
Hi sonam, I am not familiar with CommerceOne or their soap product. I'm going to guess it's not soap compliant. when you said soap sampler, did you mean webservice sampler or soap/xml-rpc sampler. If you were using the soap/xml-rpc sampler I don't know it well enough to say why it didn't work. If you were using the webservice sampler, the message body typically looks like this. ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Body doInference xmlns=http://tempuri.org/; testone two three/test /doInference /soap:Body /soap:Envelope Your message has to be soap compliant for the webservice sampler to work. It would be beneficial to post a sampler message. It's a bit hard to tell exactly what this soap service expects/requires from the details you've provided so far. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Thanks Peter. I just tried the SOAP sampler with that document but the receiving server spits out an error - possibly because of 'incorrect' HTTP header used by SOAP sampler (the document isn't really XML). Unfortunately, I can't find out exactly what's wrong since 'View Results Tree' only shows HTTP response headers. Does anyone know offhand of a JMeter debug level that dumps HTTP *request headers* to jmeter.log? (I tried 'jmeter -Ljmeter=DEBUG' but it only dumps the request body, not the request headers.) It would be better if the HTTP sampler added the facility to submit the contents of a textbox or a file. In combination with the HTTP header manager, any kind of HTTP POST would be possible (including the document below - a 'CommerceOne envelope') With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:10 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler the webservice sampler uses apache soap. the soap API requires the message meet soap requirements. the Soap/xml-rpc may be able to handle it. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Hi guys - The main reason I suggested enhancing the HTTP sampler instead was so it can POST complex documents like the one below. It is not a XML document, and the content type is not 'text/xml'. Correct me if I am wrong, but I think none of the current samplers (HTTP, SOAP and webservices samplers) can POST this document: _ Message-ID: [EMAIL PROTECTED] Date: Tue, 13 Jan 2004 13:50:47 +1100 (GMT+11:00) Mime-Version: 1.0 Content-Type: multipart/related; boundary==_Part_187_175861948.1073962247153 Content-ID: c5732f42-78e6-1000-93a0-ac1001760001 x-Date-Sent: 13 Jan 2004 13:50:47 GMT+11:00 referenceId: x-Document-Type: Error ... --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=Error; ns=urn:x- ... Error.../Error --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=catalog; ... !DOCTYPE ... ... _ Peter - Thanks - the Dec 29 CVS didn't have the webservices sampler, but the 1.9.1. stable release has an alpha version of your webservices sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 2:29 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, please take a look at the webservices sampler. It uses Apache soap driver. it can read xml envelope from text area, a file or randomly select files from a directory. it's been tested with .NET webservices. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Well, I may be missing something... (so do correct me.) However, if all that SOAP sampler does is: 1. Set content-type=text/xml 2. POST contents of it's textbox with no parameters ... it would be better to bundle that functionality into the HTTP sampler because: a. The HTTP sampler is more mature (as you said) b. It has more functionality. For e.g.: redirects/keep-alives (though I don't know if these are applicable to XML POSTs
RE: Suggestion for enhancing 'HTTP Request' sampler
I took a quick look at CommerceOne docSOAP sample. If the soap service you're trying to test is similar to the examples in CommerceOne docSOAP, then it probably isn't going to work. for one thing, CommerceOne uses env:Envelope. the sample they provide is this. env:Envelope env:Header Manifest xmlns=rrn:org.soapextensions:schemas/highperformancesoap/manifest/v1_0/Manifest.x sd xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:c1man=rrn:org.soapextensions:schemas/highperformancesoap/manifest/v1_0/Mani fest.xsd rootReference=f2dc4b1a-787f-1000-a558-0a0a02770001 actor=publicid:com.commerceone:WebService; mustunderstand=1 Reference Id=f2dc4b1a-787f-1000-a558-0a0a02770001 partName=Order Location c1man:href=/Envelope/Body/Order container=body / PartInfo docId=publicid:org.xCBL:schemas/XCBL35/Order; contentType=text/xml XMLInfo DocSchemapubliccid:org.xCBL:schemas/XCBL35/Order.xsd/DocSchema SchemaLanguagehttp://www.w3c.org/2001/XMLSchema/SchemaLanguage Prolog![CDATA[?xml version=1.0?]]/Prolog /XMLInfo PartDescription xml:lang=us-enOrder 35 Sample/PartDescription /PartInfo /Reference /Manifest /env:Header env:Body ... /env:Body /env:Envelope I've never tried using a message like this, but apache soap probably isn't going to work with it. Their approach looks similar to some of the webservices examples in the Java WebServices Development Pack (JWSDP). I'm going to guess that to get it to work, the sampler would have to use the standard JWSDP tools. Keep in mind there's a wide variety of soap services and many of them are not compatible. In fact, webservices built with .NET, JWSDP, and IBM webservices take lots of work to get them to work together. In any case, if you provide more information, I can help you figure out what is wrong. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Thanks Peter. I just tried the SOAP sampler with that document but the receiving server spits out an error - possibly because of 'incorrect' HTTP header used by SOAP sampler (the document isn't really XML). Unfortunately, I can't find out exactly what's wrong since 'View Results Tree' only shows HTTP response headers. Does anyone know offhand of a JMeter debug level that dumps HTTP *request headers* to jmeter.log? (I tried 'jmeter -Ljmeter=DEBUG' but it only dumps the request body, not the request headers.) It would be better if the HTTP sampler added the facility to submit the contents of a textbox or a file. In combination with the HTTP header manager, any kind of HTTP POST would be possible (including the document below - a 'CommerceOne envelope') With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:10 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler the webservice sampler uses apache soap. the soap API requires the message meet soap requirements. the Soap/xml-rpc may be able to handle it. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Hi guys - The main reason I suggested enhancing the HTTP sampler instead was so it can POST complex documents like the one below. It is not a XML document, and the content type is not 'text/xml'. Correct me if I am wrong, but I think none of the current samplers (HTTP, SOAP and webservices samplers) can POST this document: _ Message-ID: [EMAIL PROTECTED] Date: Tue, 13 Jan 2004 13:50:47 +1100 (GMT+11:00) Mime-Version: 1.0 Content-Type: multipart/related; boundary==_Part_187_175861948.1073962247153 Content-ID: c5732f42-78e6-1000-93a0-ac1001760001 x-Date-Sent: 13 Jan 2004 13:50:47 GMT+11:00 referenceId: x-Document-Type: Error ... --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=Error; ns=urn:x- ... Error.../Error --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=catalog; ... !DOCTYPE ... ... _ Peter - Thanks - the Dec 29 CVS didn't have the webservices sampler, but the 1.9.1. stable release has an alpha version of your webservices sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 2:29 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, please take a look at the webservices sampler
RE: Suggestion for enhancing 'HTTP Request' sampler
Hi Peter - thanks for all your inputs! Sorry man - the commerceone document I included in the message below isn't SOAP, or even XML at all - it's an older, MIME-lookalike type of format used by most CommerceOne Marketsites. I didn't mean to imply that the Webservices sampler or the SOAP/XML-RPC samplers should be able to handle that document - they shouldn't. I was pointing out that no current JMeter sampler could POST that document and an enhancement to the regular HTTP sampler would enable that document, and any other document to be posted by the regular HTTP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 January 2004 2:14 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler I took a quick look at CommerceOne docSOAP sample. If the soap service you're trying to test is similar to the examples in CommerceOne docSOAP, then it probably isn't going to work. for one thing, CommerceOne uses env:Envelope. the sample they provide is this. env:Envelope env:Header Manifest xmlns=rrn:org.soapextensions:schemas/highperformancesoap/manifest/v1_0/ Ma nifest.x sd xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:c1man=rrn:org.soapextensions:schemas/highperformancesoap/manifest /v 1_0/Mani fest.xsd rootReference=f2dc4b1a-787f-1000-a558-0a0a02770001 actor=publicid:com.commerceone:WebService; mustunderstand=1 Reference Id=f2dc4b1a-787f-1000-a558-0a0a02770001 partName=Order Location c1man:href=/Envelope/Body/Order container=body / PartInfo docId=publicid:org.xCBL:schemas/XCBL35/Order; contentType=text/xml XMLInfo DocSchemapubliccid:org.xCBL:schemas/XCBL35/Order.xsd/DocSchema SchemaLanguagehttp://www.w3c.org/2001/XMLSchema/SchemaLanguage Prolog![CDATA[?xml version=1.0?]]/Prolog /XMLInfo PartDescription xml:lang=us-enOrder 35 Sample/PartDescription /PartInfo /Reference /Manifest /env:Header env:Body ... /env:Body /env:Envelope I've never tried using a message like this, but apache soap probably isn't going to work with it. Their approach looks similar to some of the webservices examples in the Java WebServices Development Pack (JWSDP). I'm going to guess that to get it to work, the sampler would have to use the standard JWSDP tools. Keep in mind there's a wide variety of soap services and many of them are not compatible. In fact, webservices built with .NET, JWSDP, and IBM webservices take lots of work to get them to work together. In any case, if you provide more information, I can help you figure out what is wrong. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Thanks Peter. I just tried the SOAP sampler with that document but the receiving server spits out an error - possibly because of 'incorrect' HTTP header used by SOAP sampler (the document isn't really XML). Unfortunately, I can't find out exactly what's wrong since 'View Results Tree' only shows HTTP response headers. Does anyone know offhand of a JMeter debug level that dumps HTTP *request headers* to jmeter.log? (I tried 'jmeter -Ljmeter=DEBUG' but it only dumps the request body, not the request headers.) It would be better if the HTTP sampler added the facility to submit the contents of a textbox or a file. In combination with the HTTP header manager, any kind of HTTP POST would be possible (including the document below - a 'CommerceOne envelope') With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:10 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler the webservice sampler uses apache soap. the soap API requires the message meet soap requirements. the Soap/xml-rpc may be able to handle it. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Hi guys - The main reason I suggested enhancing the HTTP sampler instead was so it can POST complex documents like the one below. It is not a XML document, and the content type is not 'text/xml'. Correct me if I am wrong, but I think none of the current samplers (HTTP, SOAP and webservices samplers) can POST this document: _ Message-ID: [EMAIL PROTECTED] Date: Tue, 13 Jan 2004 13:50:47 +1100 (GMT+11:00) Mime-Version: 1.0 Content-Type: multipart/related; boundary==_Part_187_175861948.1073962247153 Content-ID: c5732f42-78e6-1000-93a0-ac1001760001 x-Date-Sent: 13 Jan 2004 13:50:47 GMT+11:00 referenceId: x-Document
RE: Suggestion for enhancing 'HTTP Request' sampler
that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. What exactly does the service require? From the previous emails I get the impression it's not just a post. If it was just a post, the soap/xml-rpc sampler should work. if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Hi Peter - thanks for all your inputs! Sorry man - the commerceone document I included in the message below isn't SOAP, or even XML at all - it's an older, MIME-lookalike type of format used by most CommerceOne Marketsites. I didn't mean to imply that the Webservices sampler or the SOAP/XML-RPC samplers should be able to handle that document - they shouldn't. I was pointing out that no current JMeter sampler could POST that document and an enhancement to the regular HTTP sampler would enable that document, and any other document to be posted by the regular HTTP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Suggestion for enhancing 'HTTP Request' sampler
that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. ... if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. Hi Peter - The SOAP sampler presents a different Content-type HTTP header which may be causing the problem. Here are the HTTP request headers used by the CommerceOne application: -- Accept=image/gif, */* Authorization=Basic xxx== Content-Length=11345 Content-type=application/x-www-form-urlencoded Host=internal_server:80 marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Mozilla/4.0 [en] (WinNT; I) -- Here are the HTTP request headers used by the JMeter SOAP/XML sampler. -- Accept=text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection=close Content-length=6782 Content-type=text/xml Host=internal_server marketparticipantid=85fhge3ea-7832-1000-a422-0aasdasd0001 User-Agent=Java/1.4.2_02 -- I used the HTTP header manager to create the special marketparticipantid=xxx header, but could not override the Content-type=text/xml header. The strange thing is that HTTP request body seemed empty when the JMeter SOAP sampler presented it. However, this could be a glitch in my CGI rather than with the SOAP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, 14 January 2004 2:54 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler that makes sense. but back to the task of how can the soap/xml-rpc sampler can be enhanced to work with CommerceOne. What exactly does the service require? From the previous emails I get the impression it's not just a post. If it was just a post, the soap/xml-rpc sampler should work. if you can list exactly what the service needs in terms of encoding, content-type, content-length, post and so on, I can take a look. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Hi Peter - thanks for all your inputs! Sorry man - the commerceone document I included in the message below isn't SOAP, or even XML at all - it's an older, MIME-lookalike type of format used by most CommerceOne Marketsites. I didn't mean to imply that the Webservices sampler or the SOAP/XML-RPC samplers should be able to handle that document - they shouldn't. I was pointing out that no current JMeter sampler could POST that document and an enhancement to the regular HTTP sampler would enable that document, and any other document to be posted by the regular HTTP sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Suggestion for enhancing 'HTTP Request' sampler
Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan ha escrit: The normal HTTP sampler seems incapable of posting XML documents using the process below (it falls down in point #2): 1. The HTTP content-type is set to text/xml. 2. The HTTP request body contains the document itself (no POST parameters are used) However, the 'SOAP/XML-RPC Request' sampler seems to handle this process well. The normal HTTP sampler can be made more generic by allowing it to POST the contents of a file or a textbox *without* POST parameters. In this case, there would be no need of the 'SOAP/XML-RPC Request' sampler - is this correct? Also, the above would make possible certain complex HTTP requests that currently are impossible with JMeter. For e.g.: CommerceOne marketsite envelopes that have multiple content-parts with no POST parameters. With regards, Sonam Chauhan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Suggestion for enhancing 'HTTP Request' sampler
Well, I may be missing something... (so do correct me.) However, if all that SOAP sampler does is: 1. Set content-type=text/xml 2. POST contents of it's textbox with no parameters ... it would be better to bundle that functionality into the HTTP sampler because: a. The HTTP sampler is more mature (as you said) b. It has more functionality. For e.g.: redirects/keep-alives (though I don't know if these are applicable to XML POSTs) The other point I had was certain HTTP POSTs are impossible - both with the HTTP sampler and the SOAP sampler. For e.g.: the multipart-MIME HTTP posts like the one CommerceOne envelope I mentioned below. If the HTTP sampler could load the actual *body* of the POST from a textbox or a file, then, in combination with the HTTP header manager, it could do anything. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:49 AM To: JMeter Developers List Subject: Re: Suggestion for enhancing 'HTTP Request' sampler Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan ha escrit: The normal HTTP sampler seems incapable of posting XML documents using the process below (it falls down in point #2): 1. The HTTP content-type is set to text/xml. 2. The HTTP request body contains the document itself (no POST parameters are used) However, the 'SOAP/XML-RPC Request' sampler seems to handle this process well. The normal HTTP sampler can be made more generic by allowing it to POST the contents of a file or a textbox *without* POST parameters. In this case, there would be no need of the 'SOAP/XML-RPC Request' sampler - is this correct? Also, the above would make possible certain complex HTTP requests that currently are impossible with JMeter. For e.g.: CommerceOne marketsite envelopes that have multiple content-parts with no POST parameters. With regards, Sonam Chauhan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Suggestion for enhancing 'HTTP Request' sampler
I would have to agree with Jordi. a typical http request is not the same thing as a RPC call. SOAP/xml-rpc gets very complicated very quickly. We already have the soap/xml-rpc and webservice sampler. The webservice sampler is being refined and improved, but it is fundamentally a different approach than soap/xml-rpc. this is primarily the result of differences in java versus .NET webservices. .NET webservices prefers document oriented messaging, whereas java webservices prefers xml-rpc. I think it is worth while to improve either soap/xml-rpc or webservices sampler. what kind of improvement were you thinking of specifically sonam? peter lin --- Jordi Salvat i Alabart [EMAIL PROTECTED] wrote: Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan ha escrit: The normal HTTP sampler seems incapable of posting XML documents using the process below (it falls down in point #2): 1. The HTTP content-type is set to text/xml. 2. The HTTP request body contains the document itself (no POST parameters are used) However, the 'SOAP/XML-RPC Request' sampler seems to handle this process well. The normal HTTP sampler can be made more generic by allowing it to POST the contents of a file or a textbox *without* POST parameters. In this case, there would be no need of the 'SOAP/XML-RPC Request' sampler - is this correct? Also, the above would make possible certain complex HTTP requests that currently are impossible with JMeter. For e.g.: CommerceOne marketsite envelopes that have multiple content-parts with no POST parameters. With regards, Sonam Chauhan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Suggestion for enhancing 'HTTP Request' sampler
Thanks Peter - Is the webservices sampler very recent? I'm working with the Dec 30 2003 CVS and it only has 8 samplers: FTP, Tomcat Access Log, HTTP, SOAP, Java, JDBC, LDAP and TCP. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 2:29 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, please take a look at the webservices sampler. It uses Apache soap driver. it can read xml envelope from text area, a file or randomly select files from a directory. it's been tested with .NET webservices. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Well, I may be missing something... (so do correct me.) However, if all that SOAP sampler does is: 1. Set content-type=text/xml 2. POST contents of it's textbox with no parameters ... it would be better to bundle that functionality into the HTTP sampler because: a. The HTTP sampler is more mature (as you said) b. It has more functionality. For e.g.: redirects/keep-alives (though I don't know if these are applicable to XML POSTs) The other point I had was certain HTTP POSTs are impossible - both with the HTTP sampler and the SOAP sampler. For e.g.: the multipart-MIME HTTP posts like the one CommerceOne envelope I mentioned below. If the HTTP sampler could load the actual *body* of the POST from a textbox or a file, then, in combination with the HTTP header manager, it could do anything. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:49 AM To: JMeter Developers List Subject: Re: Suggestion for enhancing 'HTTP Request' sampler Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan ha escrit: The normal HTTP sampler seems incapable of posting XML documents using the process below (it falls down in point #2): 1. The HTTP content-type is set to text/xml. 2. The HTTP request body contains the document itself (no POST parameters are used) However, the 'SOAP/XML-RPC Request' sampler seems to handle this process well. The normal HTTP sampler can be made more generic by allowing it to POST the contents of a file or a textbox *without* POST parameters. In this case, there would be no need of the 'SOAP/XML-RPC Request' sampler - is this correct? Also, the above would make possible certain complex HTTP requests that currently are impossible with JMeter. For e.g.: CommerceOne marketsite envelopes that have multiple content-parts with no POST parameters. With regards, Sonam Chauhan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Suggestion for enhancing 'HTTP Request' sampler
I wrote the sampler back during the summer. the webservice sampler should be right after soap/xml-rpc. I just fixed a bug for proxy support reported by Peter Reid. if you get the latest CVS and build it, you'll se the latest version. peter lin --- Sonam Chauhan [EMAIL PROTECTED] wrote: Thanks Peter - Is the webservices sampler very recent? I'm working with the Dec 30 2003 CVS and it only has 8 samplers: FTP, Tomcat Access Log, HTTP, SOAP, Java, JDBC, LDAP and TCP. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 2:29 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, please take a look at the webservices sampler. It uses Apache soap driver. it can read xml envelope from text area, a file or randomly select files from a directory. it's been tested with .NET webservices. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Well, I may be missing something... (so do correct me.) However, if all that SOAP sampler does is: 1. Set content-type=text/xml 2. POST contents of it's textbox with no parameters ... it would be better to bundle that functionality into the HTTP sampler because: a. The HTTP sampler is more mature (as you said) b. It has more functionality. For e.g.: redirects/keep-alives (though I don't know if these are applicable to XML POSTs) The other point I had was certain HTTP POSTs are impossible - both with the HTTP sampler and the SOAP sampler. For e.g.: the multipart-MIME HTTP posts like the one CommerceOne envelope I mentioned below. If the HTTP sampler could load the actual *body* of the POST from a textbox or a file, then, in combination with the HTTP header manager, it could do anything. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:49 AM To: JMeter Developers List Subject: Re: Suggestion for enhancing 'HTTP Request' sampler Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan ha escrit: The normal HTTP sampler seems incapable of posting XML documents using the process below (it falls down in point #2): 1. The HTTP content-type is set to text/xml. 2. The HTTP request body contains the document itself (no POST parameters are used) However, the 'SOAP/XML-RPC Request' sampler seems to handle this process well. The normal HTTP sampler can be made more generic by allowing it to POST the contents of a file or a textbox *without* POST parameters. In this case, there would be no need of the 'SOAP/XML-RPC Request' sampler - is this correct? Also, the above would make possible certain complex HTTP requests that currently are impossible with JMeter. For e.g.: CommerceOne marketsite envelopes that have multiple content-parts with no POST parameters. With regards, Sonam Chauhan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Suggestion for enhancing 'HTTP Request' sampler
Hi guys - The main reason I suggested enhancing the HTTP sampler instead was so it can POST complex documents like the one below. It is not a XML document, and the content type is not 'text/xml'. Correct me if I am wrong, but I think none of the current samplers (HTTP, SOAP and webservices samplers) can POST this document: _ Message-ID: [EMAIL PROTECTED] Date: Tue, 13 Jan 2004 13:50:47 +1100 (GMT+11:00) Mime-Version: 1.0 Content-Type: multipart/related; boundary==_Part_187_175861948.1073962247153 Content-ID: c5732f42-78e6-1000-93a0-ac1001760001 x-Date-Sent: 13 Jan 2004 13:50:47 GMT+11:00 referenceId: x-Document-Type: Error ... --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=Error; ns=urn:x- ... Error.../Error --=_Part_187_175861948.1073962247153 Content-Type: application/xml; owner=x-commerceone; version=1.0; type=catalog; ... !DOCTYPE ... ... _ Peter - Thanks - the Dec 29 CVS didn't have the webservices sampler, but the 1.9.1. stable release has an alpha version of your webservices sampler. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: peter lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 2:29 PM To: JMeter Developers List Subject: RE: Suggestion for enhancing 'HTTP Request' sampler hi sonam, please take a look at the webservices sampler. It uses Apache soap driver. it can read xml envelope from text area, a file or randomly select files from a directory. it's been tested with .NET webservices. peter --- Sonam Chauhan [EMAIL PROTECTED] wrote: Well, I may be missing something... (so do correct me.) However, if all that SOAP sampler does is: 1. Set content-type=text/xml 2. POST contents of it's textbox with no parameters ... it would be better to bundle that functionality into the HTTP sampler because: a. The HTTP sampler is more mature (as you said) b. It has more functionality. For e.g.: redirects/keep-alives (though I don't know if these are applicable to XML POSTs) The other point I had was certain HTTP POSTs are impossible - both with the HTTP sampler and the SOAP sampler. For e.g.: the multipart-MIME HTTP posts like the one CommerceOne envelope I mentioned below. If the HTTP sampler could load the actual *body* of the POST from a textbox or a file, then, in combination with the HTTP header manager, it could do anything. With regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-9335-0725, Fax: 9335-0753, Email: [EMAIL PROTECTED] -Original Message- From: Jordi Salvat i Alabart [mailto:[EMAIL PROTECTED] Sent: Tuesday, 13 January 2004 10:49 AM To: JMeter Developers List Subject: Re: Suggestion for enhancing 'HTTP Request' sampler Why can't we keep this function with the SOAP sampler? I agree the SOAP sampler is poor and buggy -- it needs to be improved. But I'm not in favour of piling up all functionalities into one single infinitely complex component. -- Salut, Jordi. En/na Sonam Chauhan ha escrit: The normal HTTP sampler seems incapable of posting XML documents using the process below (it falls down in point #2): 1. The HTTP content-type is set to text/xml. 2. The HTTP request body contains the document itself (no POST parameters are used) However, the 'SOAP/XML-RPC Request' sampler seems to handle this process well. The normal HTTP sampler can be made more generic by allowing it to POST the contents of a file or a textbox *without* POST parameters. In this case, there would be no need of the 'SOAP/XML-RPC Request' sampler - is this correct? Also, the above would make possible certain complex HTTP requests that currently are impossible with JMeter. For e.g.: CommerceOne marketsite envelopes that have multiple content-parts with no POST parameters. With regards, Sonam Chauhan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
