You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Scott Cederberg <ce...@gmail.com> on 2007/02/03 06:49:27 UTC
spurious content from SOAP/XML-RPC Request
Hello,
I am trying to use JMeter's SOAP/XML-RPC Request sampler to send
SOAP requests. I'm having trouble, and one problem appears to be that
the request contains things it shouldn't. A sample request captured
by netcat appears below. It seems to me that the line saying "36a"
that comes between the HTTP headers and the XML body of the request
shouldn't be there; nor should the blank line and the line saying "0"
that follow the XML.
Does anyone know why these are being sent in the request and how I
might stop them?
Thanks.
Scott
POST /soap-path/ HTTP/1.1
Connection: close
Accept: text/xml
Accept: multipart/*
Content-Length: 873
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:Path/To/Soap#mySoapAction"
User-Agent: Jakarta Commons-HttpClient/3.0.1
Host: localhost:8181
36a
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><namesp1:mySoapAction
xmlns:namesp1="urn:Snip/Snip/Snip"><c-gensym3><ignorestates
xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="xsd:int[2]"><item
xsi:type="xsd:int">-1001</item><item
xsi:type="xsd:int">1110</item></ignorestates><mytagone
xsi:type="xsd:string">QP21533260</mytagone><mytagtwo
xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="xsd:int[1]"><item
xsi:type="xsd:int">76604</item></mytagtwo></c-gensym3></namesp1:mySoapAction></SOAP-ENV:Body></SOAP-ENV:Envelope>
0
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by git <gi...@cubicalland.com>.
OK - I'll look into this in more detail - as I need to know the answer
for the TAG.net project I own. I'll report back to the list when I have
a definitive answer (if there is one).
Cheers
AJ
On Tue, 2007-02-06 at 10:22 +0000, sebb wrote:
> I thought Content-Length and chunked encoding were mutually exclusive?
>
> If so, and SOAP insists on Content-Length, then this means that
> chunked is not allowed by SOAP.
>
> I guess this needs to be looked at further.
>
> On 06/02/07, git <gi...@cubicalland.com> wrote:
> > Seb,
> >
> > I am not expert on SOAP, however it would appear that the XML-RPC spec
> > does not preclude chunked encoding, but it does insist on content
> > length. I only say this to back up your point, that having both is not
> > a bug, but is probably not what most server implementations would be
> > expecting.
> >
> > AJ
> >
> > On Mon, 2007-02-05 at 23:53 +0000, sebb wrote:
> >
> > > Just for completeness: turns out it's not a bug.
> > >
> > > However I have changed the SOAP-RPC sampler to not use chunked
> > > encoding when sending data supplied in the text box.
> > >
> > > On 05/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > > I have opened a bug regarding this issue and attached a JMX file that
> > > > reproduces the problem. The bug is #41536.
> > > >
> > > >
> > > > Scott
> > > >
> > > > On 2/4/07, sebb <se...@gmail.com> wrote:
> > > > > On 04/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > > > > On 2/3/07, sebb <se...@gmail.com> wrote:
> > > > > > > You'e right - sorry, I misread the headers:
> > > > > > >
> > > > > > > Accept: multipart/*
> > > > > > > Content-Length: 873
> > > > > > > Content-Type: text/xml; charset=utf-8
> > > > > > > SOAPAction: "urn:Path/To/Soap#mySoapAction"
> > > > > > > User-Agent: Jakarta Commons-HttpClient/3.0.1
> > > > > > >
> > > > > > > It does seem odd that there are apparent part length markers.
> > > > > > > There is already a content length header which should mean that the
> > > > > > > part sizes are not needed.
> > > > > > >
> > > > > > > Which version of JMeter are you using?
> > > > > >
> > > > > > I'm using JMeter version 2.2.
> > > > > >
> > > > > > I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
> > > > > > library, which the HTTP Sampler that I've used previously is not. I
> > > > > > tried using the HTTP Sampler HTTPClient to see if it also inserted
> > > > > > part sizes into a POST request, which it did not on the request I
> > > > > > tried.
> > > > >
> > > > > Looks like a bug in JMeter then, so please create a Bugzilla issue,
> > > > > and attach (*) any relevant files such as jmeter.log and the jmx file
> > > > > (scrub any private data first!). If you can provide a script that
> > > > > shows the fault with a public SOAP server that would be ideal.
> > > > >
> > > > > (*) you need to create the issue before you can attach anything.
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >
> > >
> > >
> >
> > www.cubicalland.com
> > www.nerds-central.blogspot.com
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
www.cubicalland.com
www.nerds-central.blogspot.com
Re: spurious content from SOAP/XML-RPC Request
Posted by sebb <se...@gmail.com>.
I thought Content-Length and chunked encoding were mutually exclusive?
If so, and SOAP insists on Content-Length, then this means that
chunked is not allowed by SOAP.
I guess this needs to be looked at further.
On 06/02/07, git <gi...@cubicalland.com> wrote:
> Seb,
>
> I am not expert on SOAP, however it would appear that the XML-RPC spec
> does not preclude chunked encoding, but it does insist on content
> length. I only say this to back up your point, that having both is not
> a bug, but is probably not what most server implementations would be
> expecting.
>
> AJ
>
> On Mon, 2007-02-05 at 23:53 +0000, sebb wrote:
>
> > Just for completeness: turns out it's not a bug.
> >
> > However I have changed the SOAP-RPC sampler to not use chunked
> > encoding when sending data supplied in the text box.
> >
> > On 05/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > I have opened a bug regarding this issue and attached a JMX file that
> > > reproduces the problem. The bug is #41536.
> > >
> > >
> > > Scott
> > >
> > > On 2/4/07, sebb <se...@gmail.com> wrote:
> > > > On 04/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > > > On 2/3/07, sebb <se...@gmail.com> wrote:
> > > > > > You'e right - sorry, I misread the headers:
> > > > > >
> > > > > > Accept: multipart/*
> > > > > > Content-Length: 873
> > > > > > Content-Type: text/xml; charset=utf-8
> > > > > > SOAPAction: "urn:Path/To/Soap#mySoapAction"
> > > > > > User-Agent: Jakarta Commons-HttpClient/3.0.1
> > > > > >
> > > > > > It does seem odd that there are apparent part length markers.
> > > > > > There is already a content length header which should mean that the
> > > > > > part sizes are not needed.
> > > > > >
> > > > > > Which version of JMeter are you using?
> > > > >
> > > > > I'm using JMeter version 2.2.
> > > > >
> > > > > I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
> > > > > library, which the HTTP Sampler that I've used previously is not. I
> > > > > tried using the HTTP Sampler HTTPClient to see if it also inserted
> > > > > part sizes into a POST request, which it did not on the request I
> > > > > tried.
> > > >
> > > > Looks like a bug in JMeter then, so please create a Bugzilla issue,
> > > > and attach (*) any relevant files such as jmeter.log and the jmx file
> > > > (scrub any private data first!). If you can provide a script that
> > > > shows the fault with a public SOAP server that would be ideal.
> > > >
> > > > (*) you need to create the issue before you can attach anything.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
> >
>
> www.cubicalland.com
> www.nerds-central.blogspot.com
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by git <gi...@cubicalland.com>.
Seb,
I am not expert on SOAP, however it would appear that the XML-RPC spec
does not preclude chunked encoding, but it does insist on content
length. I only say this to back up your point, that having both is not
a bug, but is probably not what most server implementations would be
expecting.
AJ
On Mon, 2007-02-05 at 23:53 +0000, sebb wrote:
> Just for completeness: turns out it's not a bug.
>
> However I have changed the SOAP-RPC sampler to not use chunked
> encoding when sending data supplied in the text box.
>
> On 05/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > I have opened a bug regarding this issue and attached a JMX file that
> > reproduces the problem. The bug is #41536.
> >
> >
> > Scott
> >
> > On 2/4/07, sebb <se...@gmail.com> wrote:
> > > On 04/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > > On 2/3/07, sebb <se...@gmail.com> wrote:
> > > > > You'e right - sorry, I misread the headers:
> > > > >
> > > > > Accept: multipart/*
> > > > > Content-Length: 873
> > > > > Content-Type: text/xml; charset=utf-8
> > > > > SOAPAction: "urn:Path/To/Soap#mySoapAction"
> > > > > User-Agent: Jakarta Commons-HttpClient/3.0.1
> > > > >
> > > > > It does seem odd that there are apparent part length markers.
> > > > > There is already a content length header which should mean that the
> > > > > part sizes are not needed.
> > > > >
> > > > > Which version of JMeter are you using?
> > > >
> > > > I'm using JMeter version 2.2.
> > > >
> > > > I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
> > > > library, which the HTTP Sampler that I've used previously is not. I
> > > > tried using the HTTP Sampler HTTPClient to see if it also inserted
> > > > part sizes into a POST request, which it did not on the request I
> > > > tried.
> > >
> > > Looks like a bug in JMeter then, so please create a Bugzilla issue,
> > > and attach (*) any relevant files such as jmeter.log and the jmx file
> > > (scrub any private data first!). If you can provide a script that
> > > shows the fault with a public SOAP server that would be ideal.
> > >
> > > (*) you need to create the issue before you can attach anything.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
>
www.cubicalland.com
www.nerds-central.blogspot.com
Re: spurious content from SOAP/XML-RPC Request
Posted by sebb <se...@gmail.com>.
Just for completeness: turns out it's not a bug.
However I have changed the SOAP-RPC sampler to not use chunked
encoding when sending data supplied in the text box.
On 05/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> I have opened a bug regarding this issue and attached a JMX file that
> reproduces the problem. The bug is #41536.
>
>
> Scott
>
> On 2/4/07, sebb <se...@gmail.com> wrote:
> > On 04/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > On 2/3/07, sebb <se...@gmail.com> wrote:
> > > > You'e right - sorry, I misread the headers:
> > > >
> > > > Accept: multipart/*
> > > > Content-Length: 873
> > > > Content-Type: text/xml; charset=utf-8
> > > > SOAPAction: "urn:Path/To/Soap#mySoapAction"
> > > > User-Agent: Jakarta Commons-HttpClient/3.0.1
> > > >
> > > > It does seem odd that there are apparent part length markers.
> > > > There is already a content length header which should mean that the
> > > > part sizes are not needed.
> > > >
> > > > Which version of JMeter are you using?
> > >
> > > I'm using JMeter version 2.2.
> > >
> > > I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
> > > library, which the HTTP Sampler that I've used previously is not. I
> > > tried using the HTTP Sampler HTTPClient to see if it also inserted
> > > part sizes into a POST request, which it did not on the request I
> > > tried.
> >
> > Looks like a bug in JMeter then, so please create a Bugzilla issue,
> > and attach (*) any relevant files such as jmeter.log and the jmx file
> > (scrub any private data first!). If you can provide a script that
> > shows the fault with a public SOAP server that would be ideal.
> >
> > (*) you need to create the issue before you can attach anything.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by Scott Cederberg <ce...@gmail.com>.
I have opened a bug regarding this issue and attached a JMX file that
reproduces the problem. The bug is #41536.
Scott
On 2/4/07, sebb <se...@gmail.com> wrote:
> On 04/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > On 2/3/07, sebb <se...@gmail.com> wrote:
> > > You'e right - sorry, I misread the headers:
> > >
> > > Accept: multipart/*
> > > Content-Length: 873
> > > Content-Type: text/xml; charset=utf-8
> > > SOAPAction: "urn:Path/To/Soap#mySoapAction"
> > > User-Agent: Jakarta Commons-HttpClient/3.0.1
> > >
> > > It does seem odd that there are apparent part length markers.
> > > There is already a content length header which should mean that the
> > > part sizes are not needed.
> > >
> > > Which version of JMeter are you using?
> >
> > I'm using JMeter version 2.2.
> >
> > I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
> > library, which the HTTP Sampler that I've used previously is not. I
> > tried using the HTTP Sampler HTTPClient to see if it also inserted
> > part sizes into a POST request, which it did not on the request I
> > tried.
>
> Looks like a bug in JMeter then, so please create a Bugzilla issue,
> and attach (*) any relevant files such as jmeter.log and the jmx file
> (scrub any private data first!). If you can provide a script that
> shows the fault with a public SOAP server that would be ideal.
>
> (*) you need to create the issue before you can attach anything.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by sebb <se...@gmail.com>.
On 04/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> On 2/3/07, sebb <se...@gmail.com> wrote:
> > You'e right - sorry, I misread the headers:
> >
> > Accept: multipart/*
> > Content-Length: 873
> > Content-Type: text/xml; charset=utf-8
> > SOAPAction: "urn:Path/To/Soap#mySoapAction"
> > User-Agent: Jakarta Commons-HttpClient/3.0.1
> >
> > It does seem odd that there are apparent part length markers.
> > There is already a content length header which should mean that the
> > part sizes are not needed.
> >
> > Which version of JMeter are you using?
>
> I'm using JMeter version 2.2.
>
> I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
> library, which the HTTP Sampler that I've used previously is not. I
> tried using the HTTP Sampler HTTPClient to see if it also inserted
> part sizes into a POST request, which it did not on the request I
> tried.
Looks like a bug in JMeter then, so please create a Bugzilla issue,
and attach (*) any relevant files such as jmeter.log and the jmx file
(scrub any private data first!). If you can provide a script that
shows the fault with a public SOAP server that would be ideal.
(*) you need to create the issue before you can attach anything.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by Scott Cederberg <ce...@gmail.com>.
On 2/3/07, sebb <se...@gmail.com> wrote:
> You'e right - sorry, I misread the headers:
>
> Accept: multipart/*
> Content-Length: 873
> Content-Type: text/xml; charset=utf-8
> SOAPAction: "urn:Path/To/Soap#mySoapAction"
> User-Agent: Jakarta Commons-HttpClient/3.0.1
>
> It does seem odd that there are apparent part length markers.
> There is already a content length header which should mean that the
> part sizes are not needed.
>
> Which version of JMeter are you using?
I'm using JMeter version 2.2.
I notice that the SOAP Sampler is using the Jakarta Commons HTTPClient
library, which the HTTP Sampler that I've used previously is not. I
tried using the HTTP Sampler HTTPClient to see if it also inserted
part sizes into a POST request, which it did not on the request I
tried.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by sebb <se...@gmail.com>.
On 03/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> On 2/3/07, sebb <se...@gmail.com> wrote:
> > (for completeness) and the 0 afterwards means there are no more parts
> > of the multipart post.
> >
>
> I don't think I'm sending a multipart post, though. Should I be? I'd
> been setting the Content-Type header to "text/xml", but when I don't
> set it at all JMeter fills in "text/xml" by default.
>
You'e right - sorry, I misread the headers:
Accept: multipart/*
Content-Length: 873
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:Path/To/Soap#mySoapAction"
User-Agent: Jakarta Commons-HttpClient/3.0.1
It does seem odd that there are apparent part length markers.
There is already a content length header which should mean that the
part sizes are not needed.
Which version of JMeter are you using?
> Scott
>
> > On 03/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > P.S. I've just figured out that the "36a" appearing before the body of
> > > the request is the length of the request body in bytes.
> > >
> > > On 2/2/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > > Hello,
> > > >
> > [...]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by Scott Cederberg <ce...@gmail.com>.
On 2/3/07, sebb <se...@gmail.com> wrote:
> (for completeness) and the 0 afterwards means there are no more parts
> of the multipart post.
>
I don't think I'm sending a multipart post, though. Should I be? I'd
been setting the Content-Type header to "text/xml", but when I don't
set it at all JMeter fills in "text/xml" by default.
Scott
> On 03/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> > P.S. I've just figured out that the "36a" appearing before the body of
> > the request is the length of the request body in bytes.
> >
> > On 2/2/07, Scott Cederberg <ce...@gmail.com> wrote:
> > > Hello,
> > >
> [...]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by sebb <se...@gmail.com>.
(for completeness) and the 0 afterwards means there are no more parts
of the multipart post.
On 03/02/07, Scott Cederberg <ce...@gmail.com> wrote:
> P.S. I've just figured out that the "36a" appearing before the body of
> the request is the length of the request body in bytes.
>
> On 2/2/07, Scott Cederberg <ce...@gmail.com> wrote:
> > Hello,
> >
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: spurious content from SOAP/XML-RPC Request
Posted by Scott Cederberg <ce...@gmail.com>.
P.S. I've just figured out that the "36a" appearing before the body of
the request is the length of the request body in bytes.
On 2/2/07, Scott Cederberg <ce...@gmail.com> wrote:
> Hello,
>
> I am trying to use JMeter's SOAP/XML-RPC Request sampler to send
> SOAP requests. I'm having trouble, and one problem appears to be that
> the request contains things it shouldn't. A sample request captured
> by netcat appears below. It seems to me that the line saying "36a"
> that comes between the HTTP headers and the XML body of the request
> shouldn't be there; nor should the blank line and the line saying "0"
> that follow the XML.
>
> Does anyone know why these are being sent in the request and how I
> might stop them?
>
> Thanks.
>
>
> Scott
>
> POST /soap-path/ HTTP/1.1
> Connection: close
> Accept: text/xml
> Accept: multipart/*
> Content-Length: 873
> Content-Type: text/xml; charset=utf-8
> SOAPAction: "urn:Path/To/Soap#mySoapAction"
> User-Agent: Jakarta Commons-HttpClient/3.0.1
> Host: localhost:8181
>
> 36a
> <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/1999/XMLSchema"
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><namesp1:mySoapAction
> xmlns:namesp1="urn:Snip/Snip/Snip"><c-gensym3><ignorestates
> xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="xsd:int[2]"><item
> xsi:type="xsd:int">-1001</item><item
> xsi:type="xsd:int">1110</item></ignorestates><mytagone
> xsi:type="xsd:string">QP21533260</mytagone><mytagtwo
> xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="xsd:int[1]"><item
> xsi:type="xsd:int">76604</item></mytagtwo></c-gensym3></namesp1:mySoapAction></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
> 0
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org