When to use which http sampler?

["Christensen, Alan" <al...@hp.com>]

I originally wrote all my scripts using the "HTTP Request" sampler.  Now
there is a second one that is called "HTTP Request HTTPClient".  What is
the advantage of using one vs the other? 

So far the "HTTP Request" sampler has worked well for my tests except
that the line speed property cannot be used with this sampler.

The "HTTP Request HTTPClient" sampler does work with the line speed
property but the current version in the December 7th nightly build
doesn't seem to work with https (parameter issue?) and doesn't
decompress pages that were requested with compression enabled.  Hence
all assertions fail.  These issues would seem to make this new sampler
not worth using unless you must take advantage of the line speed
property.  Are there any advantages of this sampler that I don't know
about?  Why was it developed?

Re: When to use which http sampler?

[sebb <se...@gmail.com>]

I realise now that it is checking for Transfer-Encoding, rather than
Content-Encoding.

Which one are you using?

On 10/12/05, sebb <se...@gmail.com> wrote:
> I've added some code to the HttpClient Sampler which hopefully handles
> gzip decompression. Not been able to test it.
>
> If you want to try it, the nightly build 2-1.20051210 contains the update.
>
> S.
> On 09/12/05, sebb <se...@gmail.com> wrote:
> > I believe it also supports NTLM authentication even when running on
> > non-Windows hosts.
> >
> > It's a lot more configurable. Adding slow connections to the default
> > implementation is hard work. The Apache implementation has proper
> > Cookie handling (though we aren't using that yet). It also has highly
> > configurable logging, should that be needed.
> >
> > However, there are some features of the original HttpSampler that have
> > not yet been implemented in the new sampler. We're trying to add them
> > as problems arise, but day jobs and other commitments can get in the
> > way...
> >
> > If there are features which don't yet work in the Apache Http Sampler,
> > please feel free to create a Bugzilla issue. Test cases are a help.
> > Patches even better...
> >
> > S.
> > On 09/12/05, Peter Lin <wo...@gmail.com> wrote:
> > > the advantage of the HTTPClient version is it supports keep alive and slow
> > > connections correctly. the default sun implementation does not and hasn't
> > > since the beginning.
> > >
> > > peter
> > >
> > >
> > > On 12/9/05, Christensen, Alan <al...@hp.com> wrote:
> > > >
> > > > I originally wrote all my scripts using the "HTTP Request" sampler.  Now
> > > > there is a second one that is called "HTTP Request HTTPClient".  What is
> > > > the advantage of using one vs the other?
> > > >
> > > > So far the "HTTP Request" sampler has worked well for my tests except
> > > > that the line speed property cannot be used with this sampler.
> > > >
> > > > The "HTTP Request HTTPClient" sampler does work with the line speed
> > > > property but the current version in the December 7th nightly build
> > > > doesn't seem to work with https (parameter issue?) and doesn't
> > > > decompress pages that were requested with compression enabled.  Hence
> > > > all assertions fail.  These issues would seem to make this new sampler
> > > > not worth using unless you must take advantage of the line speed
> > > > property.  Are there any advantages of this sampler that I don't know
> > > > about?  Why was it developed?
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

Re: When to use which http sampler?

[sebb <se...@gmail.com>]

I've added some code to the HttpClient Sampler which hopefully handles
gzip decompression. Not been able to test it.

If you want to try it, the nightly build 2-1.20051210 contains the update.

S.
On 09/12/05, sebb <se...@gmail.com> wrote:
> I believe it also supports NTLM authentication even when running on
> non-Windows hosts.
>
> It's a lot more configurable. Adding slow connections to the default
> implementation is hard work. The Apache implementation has proper
> Cookie handling (though we aren't using that yet). It also has highly
> configurable logging, should that be needed.
>
> However, there are some features of the original HttpSampler that have
> not yet been implemented in the new sampler. We're trying to add them
> as problems arise, but day jobs and other commitments can get in the
> way...
>
> If there are features which don't yet work in the Apache Http Sampler,
> please feel free to create a Bugzilla issue. Test cases are a help.
> Patches even better...
>
> S.
> On 09/12/05, Peter Lin <wo...@gmail.com> wrote:
> > the advantage of the HTTPClient version is it supports keep alive and slow
> > connections correctly. the default sun implementation does not and hasn't
> > since the beginning.
> >
> > peter
> >
> >
> > On 12/9/05, Christensen, Alan <al...@hp.com> wrote:
> > >
> > > I originally wrote all my scripts using the "HTTP Request" sampler.  Now
> > > there is a second one that is called "HTTP Request HTTPClient".  What is
> > > the advantage of using one vs the other?
> > >
> > > So far the "HTTP Request" sampler has worked well for my tests except
> > > that the line speed property cannot be used with this sampler.
> > >
> > > The "HTTP Request HTTPClient" sampler does work with the line speed
> > > property but the current version in the December 7th nightly build
> > > doesn't seem to work with https (parameter issue?) and doesn't
> > > decompress pages that were requested with compression enabled.  Hence
> > > all assertions fail.  These issues would seem to make this new sampler
> > > not worth using unless you must take advantage of the line speed
> > > property.  Are there any advantages of this sampler that I don't know
> > > about?  Why was it developed?
> > >
> > >
> > >
> > >
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

Re: When to use which http sampler?

[sebb <se...@gmail.com>]

I believe it also supports NTLM authentication even when running on
non-Windows hosts.

It's a lot more configurable. Adding slow connections to the default
implementation is hard work. The Apache implementation has proper
Cookie handling (though we aren't using that yet). It also has highly
configurable logging, should that be needed.

However, there are some features of the original HttpSampler that have
not yet been implemented in the new sampler. We're trying to add them
as problems arise, but day jobs and other commitments can get in the
way...

If there are features which don't yet work in the Apache Http Sampler,
please feel free to create a Bugzilla issue. Test cases are a help.
Patches even better...

S.
On 09/12/05, Peter Lin <wo...@gmail.com> wrote:
> the advantage of the HTTPClient version is it supports keep alive and slow
> connections correctly. the default sun implementation does not and hasn't
> since the beginning.
>
> peter
>
>
> On 12/9/05, Christensen, Alan <al...@hp.com> wrote:
> >
> > I originally wrote all my scripts using the "HTTP Request" sampler.  Now
> > there is a second one that is called "HTTP Request HTTPClient".  What is
> > the advantage of using one vs the other?
> >
> > So far the "HTTP Request" sampler has worked well for my tests except
> > that the line speed property cannot be used with this sampler.
> >
> > The "HTTP Request HTTPClient" sampler does work with the line speed
> > property but the current version in the December 7th nightly build
> > doesn't seem to work with https (parameter issue?) and doesn't
> > decompress pages that were requested with compression enabled.  Hence
> > all assertions fail.  These issues would seem to make this new sampler
> > not worth using unless you must take advantage of the line speed
> > property.  Are there any advantages of this sampler that I don't know
> > about?  Why was it developed?
> >
> >
> >
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

Re: When to use which http sampler?

[Peter Lin <wo...@gmail.com>]

the advantage of the HTTPClient version is it supports keep alive and slow
connections correctly. the default sun implementation does not and hasn't
since the beginning.

peter


On 12/9/05, Christensen, Alan <al...@hp.com> wrote:
>
> I originally wrote all my scripts using the "HTTP Request" sampler.  Now
> there is a second one that is called "HTTP Request HTTPClient".  What is
> the advantage of using one vs the other?
>
> So far the "HTTP Request" sampler has worked well for my tests except
> that the line speed property cannot be used with this sampler.
>
> The "HTTP Request HTTPClient" sampler does work with the line speed
> property but the current version in the December 7th nightly build
> doesn't seem to work with https (parameter issue?) and doesn't
> decompress pages that were requested with compression enabled.  Hence
> all assertions fail.  These issues would seem to make this new sampler
> not worth using unless you must take advantage of the line speed
> property.  Are there any advantages of this sampler that I don't know
> about?  Why was it developed?
>
>
>
>