On 21 August 2012 17:34, Immanuel Hayden <immanuel.hay...@gmail.com> wrote: > I personally rely on HC4 as it allows me to put more than just the host in > the host field (ie. also part of the address)
That's probably a bug in JMeter ... > ... why I do this? I mostly > test our API which is running on (test.)api.xyz.com/Vx (x = version) > whereas our devs partially have it run on their local machines just as > localhost (so, without the Vx-subdirectory). Also the version almost never > changes (and if it does it usually creates breaking changes which call for > refactoring most TCs anyhow), so the part I put in the host line is > essentially a static string that would only add overhead in the other > fields. > > Sidenote: personally I don't understand why we have a split host and > address field anyhow and not just one line (which then can be split on the > first slash or something - there is surely a lib for this - should the > http-implementation require so), but that's another story ;) Just put the full URL in the Path field. > On Tue, Aug 21, 2012 at 6:11 PM, Milamber <milam...@apache.org> wrote: > >> Hello, >> >> Regardless Cookie Manager (HC3/HC4), It's would be a good thing to change >> the default implementation of the HTTP client in the HTTP request. >> >> Today, the default is the HTTP "Java" request, but it has the following >> issues: >> * HTTPS less efficient than HC3 or HC4 >> * No possibility to change source IP >> >> Implementation HC 3.1 is stable and reliable >> >> The implementation HC4 is (relatively) recent in JMeter. And there were >> some anomalies in the past. >> >> I think the next version of JMeter could have HC3.1 as a default >> implementation. (Or if you want to be bold, have HC4) >> >> What's is your opinion? >> >> >> Milamber >>
