other possible solution is
Test Plan
- Threads Group
- HTTP Request Sampler 1
- HTTP Header Manager (using variable myHeaderVar, for example)
- BeanShell Pre-Processor (modify myHeaderVar variable value)
- HTTP Request Sampler 2
- HTTP Header Manager (using variable myHeaderVar, for example)
- BeanShell Pre-Processor (modify myHeaderVar variable value)
Regards.
Flávio Cysne
2012/10/15 David Luu <[email protected]>
> So you can set headers via HTTP Header Manager as a child of a HTTP request
> sampler? That's good to know, simpler setup.
>
> My alternate solution was to group setting the header (via HTTP Header
> Manager) and the sampler together as a logical unit (as children of) using
> a Simple Controller.
>
> On Mon, Oct 15, 2012 at 6:31 AM, Sławomir Kluz <[email protected]
> >wrote:
>
> > Hi,
> >
> > In your case, set Host-header should be a child of HTTPSampler.
> >
> > 2012/10/15 Mikhail T. <[email protected]>:
> > > Hello!
> > >
> > > I need to test several different virtual hosts on the same physical
> > server
> > > (IP-address). I'm trying to use the "HTTP header component":
> > >
> > > Set Host-header to vhost1
> > > HTTP-sampler one
> > > Set Host-header to vhost2
> > > HTTP-sampler two
> > >
> > > Unfortunately, the second HTTP-sampler still runs with Host-header set
> to
> > > vhost1... I guess, this is another manifestation of the config vs.
> > something
> > > else components?.. How can I do, what I need?
> > >
> > > Currently, I work around the problem by placing the two tests in
> > different
> > > thread-groups. Is that the only way?
> > >
> > > Perhaps, request-headers should be properties of the sampler entirely?
> > > Thanks,
> > >
> > > -mi
> > >
> >
> >
> >
> > --
> > Sławomir Kluz
> > [email protected]
> > --
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
