Oh, I see. Sorry, misread that.

I also misread the sampler screen - the proxy details are present, but
I did not notice them as they were off the bottom.

Try adding an Authorisation Manager - it does use that in the code,
but I'm not sure if that applies to the proxy or the server the other
side of the proxy.

If this does not work, then raise a Bugzilla issue

S

On 25/08/06, Karr, David <[EMAIL PROTECTED]> wrote:
The problem is not the proxy host and port.  The problem is the user and
password.  There doesn't appear to be any reference to a system property
for that.

> -----Original Message-----
> From: sebb [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 25, 2006 7:16 AM
> To: JMeter Users List
> Subject: Re: Unable to get out through authenticated proxy
>
> I think you are right - there is code to handle a proxy, but
> no entry in the GUI to set the properties...
>
> However, if the values are not set, it seems that it looks at
> the system properties:
>
> http.proxyHost
> http.proxyPort
>
> Try these - the -D flag can be used, or the system.properties file.
>
> Looks like a bug should be raised; the sampler should
> probably behave like the Apache HttpClient version, which
> supports command-line proxy definitions and proxy exclusions
> via jmeter.properties.
>
> I can't see the point of defining the proxy on the GUI, so
> that code could probably be removed...
>
> On 25/08/06, Sen, Kakoli <[EMAIL PROTECTED]> wrote:
> > Hi Sebb/Peter,
> >     With 2.2 WebService(SOAP), I am also facing problem
> with external web-service where we have to go though the HTTP
> proxy. I too believe it doesn't take proxy credentials from
> command-line. And the GUI does not give any way to specify
> them. Is there a bug raised on this?
> >
> > Regards,
> > Kakoli
> >
> >
> > -----Original Message-----
> > From: Karr, David [mailto:[EMAIL PROTECTED]
> > Sent: Friday, August 25, 2006 7:17 AM
> > To: JMeter Users List
> > Subject: RE: Unable to get out through authenticated proxy
> >
> >
> > The WebService(SOAP) choice doesn't work either, for a
> different reason.
> > Apparently that doesn't use the command-line arguments for
> the proxy
> > configuration, it uses the parameters specified in the
> sampler itself.
> > That's fine, but there's no proxyuser or proxypassword
> fields.  When I
> > run it, it just gets back a proxy auth required header.
> >
> > > -----Original Message-----
> > > From: sebb [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, August 24, 2006 7:30 AM
> > > To: JMeter Users List
> > > Subject: Re: Unable to get out through authenticated proxy
> > >
> > > I though the WSDL was only used to populate the other fields?
> > >
> > > Can't one just populate them directly?
> > >
> > > On 24/08/06, Karr, David <[EMAIL PROTECTED]> wrote:
> > > > I'm seeing the problem with both the SOAP/XML-RPC Request and
> > > > HTTPClient request.  I don't have a WSDL, so I can't use the
> > > > WebService(SOAP) request.
> > > >
> > > > > -----Original Message-----
> > > > > From: Sen, Kakoli [mailto:[EMAIL PROTECTED]
> > > > > Sent: Wednesday, August 23, 2006 10:14 PM
> > > > > To: JMeter Users List
> > > > > Subject: RE: Unable to get out through authenticated proxy
> > > > >
> > > > > Hi,
> > > > >   Is it through the 'SOAP/XML-RPC Request' or
> 'WebService(SOAP)'
> > > > > Request?
> > > > > So in 2.2, these requests cannot pierce authenticated proxy?
> > > > >
> > > > > Regards,
> > > > > Kakoli
> > > > >
> > > > > -----Original Message-----
> > > > > From: Karr, David [mailto:[EMAIL PROTECTED]
> > > > > Sent: Wednesday, August 23, 2006 2:59 AM
> > > > > To: JMeter Users List
> > > > > Subject: Unable to get out through authenticated proxy
> > > > >
> > > > >
> > > > > I've been making progress on testing the service that
> runs on my
> > > > > localhost, but I'm also trying to test an external
> > > service, through
> > > > > our authenticated proxy.
> > > > >
> > > > > I found that the request wasn't going anywhere.  I
> > > monitored it with
> > > > > etheral, and it never tried to hit the proxy or the
> > > downstream host.
> > > > > I turned on all the debug levels, but the log file
> didn't show
> > > > > me anything meaningful.
> > > > >
> > > > > I finally thought to add a "Save results to file"
> > > > > postprocessor.  When I inspected the file, I found this:
> > > > >
> > > > > java.lang.IllegalArgumentException: Host may not be null
> > > > >       at
> > > > > org.apache.commons.httpclient.NTCredentials.<init>(NTCredentia
> > > > > ls.java:83
> > > > > )
> > > > >       at
> > > > > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.setupConn
> > > > > ection(HTT
> > > > > PSampler2.java:274)
> > > > >       at
> > > > > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HT
> > > > > TPSampler2
> > > > > .java:518)
> > > > >       at
> > > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample
> > > > > (HTTPSampl
> > > > > erBase.java:658)
> > > > >       at
> > > > > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample
> > > > > (HTTPSampl
> > > > > erBase.java:647)
> > > > >       at
> > > > >
> org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:247)
> > > > >       at java.lang.Thread.run(Thread.java:534)
> > > > >
> > > > > I looked at the code for HTTPSampler2, and it has this code:
> > > > >
> > > > > ------------
> > > > >             if (PROXY_USER.length() > 0){
> > > > >                 httpClient.getState().setProxyCredentials(
> > > > >                     new
> > > > > AuthScope(PROXY_HOST,PROXY_PORT,null,AuthScope.ANY_SCHEME),
> > > > >                     // NT Includes other types of Credentials
> > > > >                     new NTCredentials(
> > > > >                             PROXY_USER,
> > > > >                             PROXY_PASS,
> > > > >                             null, // "thishost",
> > > > >                             "" // domain
> > > > >                 ));
> > > > >             }
> > > > > ------------
> > > > >
> > > > > I looked at the javadoc for NTCredentials, and it
> > > specifically says
> > > > > that the hostname cannot be null.
> > > > >
> > > > >
> > >
> --------------------------------------------------------------------
> > > > > - To unsubscribe, e-mail:
> > > [EMAIL PROTECTED]
> > > > > For additional commands, e-mail:
> > > [EMAIL PROTECTED]
> > > > >
> > > > >
> > > > >
> > >
> --------------------------------------------------------------------
> > > > > - To unsubscribe, e-mail:
> > > [EMAIL PROTECTED]
> > > > > For additional commands, e-mail:
> > > [EMAIL PROTECTED]
> > > > >
> > > > >
> > > >
> > > >
> > >
> --------------------------------------------------------------------
> > > -
> > > > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > > > For additional commands, e-mail:
> > > > [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> --------------------------------------------------------------------
> > > - To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> [EMAIL PROTECTED]
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to