Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of sebbaz@gmail.com designates
 66.249.92.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Qe7k+6ivfDeLH3lv10y90j/Akj727GjPl+3NcwrpURI7yVMuNLgVymUZVMoqUqXaBETrqAt+wa00K0hQdZ/dvXuVcJJMjyOaj634Et6HZ3iUnQMTjiuYIEMfkg9dbryVIP2UAEF+vHupjCn6aulBjK1iPAXcwnRkK7jWt8aUFWo=
Message-ID: <25aac9fc0702060222m6118688gf11dbe35ca9a5a3a@mail.gmail.com>
Date: Tue, 6 Feb 2007 10:22:14 +0000
From: sebb <sebbaz@gmail.com>
To: "JMeter Users List" <jmeter-user@jakarta.apache.org>, git@cubicalland.com
Subject: Re: spurious content from SOAP/XML-RPC Request
In-Reply-To: <1170749451.5176.2.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5b0b6bb10702022149w6291938dj4f5317bdb2d410b1@mail.gmail.com>
	 <5b0b6bb10702022158s11ff2337i104c5a0ddaea7460@mail.gmail.com>
	 <25aac9fc0702030244p71eb3405ybec3e0b1d0ca06b6@mail.gmail.com>
	 <5b0b6bb10702031406h68467767xff492fe429844819@mail.gmail.com>
	 <25aac9fc0702031449g2cdef84cjd868ebe14be1f640@mail.gmail.com>
	 <5b0b6bb10702031806s30ddbe90k2c6f0d04f114923a@mail.gmail.com>
	 <25aac9fc0702040357g556251cak886874a1d58bcef@mail.gmail.com>
	 <5b0b6bb10702041737o5cdd7a45ka49c33f97f87163e@mail.gmail.com>
	 <25aac9fc0702051553j1bd7ae08s967d90be05a990f5@mail.gmail.com>
	 <1170749451.5176.2.camel@localhost>

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 <git@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 <cederber@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 <sebbaz@gmail.com> wrote:
> > > > On 04/02/07, Scott Cederberg <cederber@gmail.com> wrote:
> > > > > On 2/3/07, sebb <sebbaz@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