HTTP Proxy Server with soap recording and derived headers

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

HTTP Proxy Server with soap recording and derived headers

Alex-2

I've hacked (and I do mean hacked, no GUI, JMeter newbie I am)
a version of HTTP proxy to also capture soap requests
and store them via SoapSampler (SOAP/XML-RPC Request)
so far so good, tweak a little bit and off I go testing.
Kudos to JMeter contributors, this was all pretty straightforward.
SoapSampler seems a bit finicky but that's for another email.

Something I don't understand is why "Browser Derived Headers"
are stored in the .jmx file for SoapSampler entries even if I unselect
Browser derived headers. HTTPSamplers recorded at the same time
don't have these entries. Seems like there is some down stream
processing to remove the sampler "HeaderManager" I'm not seeing
somewhere.
Any pointers?

I discovered this in the process of doing the following in
....http.Proxy.run()

    // Also don't care for carrying authorization into temp
    // stored vars, why is this captured when Capture Headers is off?
    headers.removeHeaderNamed("Authorization");

as I need to inject authorization in different ways and can't have it
hard coded into my tests.

Alex


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: HTTP Proxy Server with soap recording and derived headers

Peter Lin
not sure why honestly, but to be clear.

there's two soap samplers

soap/xml-rpc
soap webservice

in the case of soap webservice sampler, it uses apache soap driver.

peter


On 5/13/05, Alex <[hidden email]> wrote:

>
> I've hacked (and I do mean hacked, no GUI, JMeter newbie I am)
> a version of HTTP proxy to also capture soap requests
> and store them via SoapSampler (SOAP/XML-RPC Request)
> so far so good, tweak a little bit and off I go testing.
> Kudos to JMeter contributors, this was all pretty straightforward.
> SoapSampler seems a bit finicky but that's for another email.
>
> Something I don't understand is why "Browser Derived Headers"
> are stored in the .jmx file for SoapSampler entries even if I unselect
> Browser derived headers. HTTPSamplers recorded at the same time
> don't have these entries. Seems like there is some down stream
> processing to remove the sampler "HeaderManager" I'm not seeing
> somewhere.
> Any pointers?
>
> I discovered this in the process of doing the following in
> ....http.Proxy.run()
>
>     // Also don't care for carrying authorization into temp
>     // stored vars, why is this captured when Capture Headers is off?
>     headers.removeHeaderNamed("Authorization");
>
> as I need to inject authorization in different ways and can't have it
> hard coded into my tests.
>
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]