Sorry, I only did one of the domains - but that should have been the
one that applied to the proxy, so not quite sure why it did not
work...

I've now done the other, and rebuilt as version 2-1.20060406.

S.
On 06/04/06, Korny Sietsma <[EMAIL PROTECTED]> wrote:
>
> The nightly build I just fetched doesn't seem to have this change - but
> it seemed like a simple thing to do, so I downloaded the nightly build
> source and re-built with the changes - and it seems to fix the problem!
>
> The changes I made were only to HTTPSampler2.java - I changed both calls
> to "new NTCredentials" to pass "" instead of null, for both the host
> and domain parameters.
>
> And now web proxies with username/password seem to work for both normal
> HTTP Samplers, and HTTPClient based samplers.
>
> Thanks for tracking this down!
>
> - Korny
>
> On 4/5/2006, "sebb" <[EMAIL PROTECTED]> wrote:
>
> >I've changed the code to pass in an empty string instead.
> >
> >If you want to test it out, the fix is in the nightly build:
> >
> >2-1.20060405
> >
> >Please let me know if that fixes it for you.
> >
> >S.
> >
> >On 05/04/06, sebb <[EMAIL PROTECTED]> wrote:
> >> OK thanks, I'll try and create a new release soon.
> >>
> >> At least we know it's trying to set up the credentials, which is
> >> part-way there...
> >>
> >> S.
> >> On 05/04/06, Korny Sietsma <[EMAIL PROTECTED]> wrote:
> >> >
> >> > Tried it - I now get the following response data:
> >> > java.lang.IllegalArgumentException: Domain may not be null
> >> >        at
> >> > org.apache.commons.httpclient.NTCredentials.<init>(NTCredentials.java:79)
> >> >        at
> >> > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.setupConnection(HTTPSampler2.java:234)
> >> >        at
> >> > org.apache.jmeter.protocol.http.sampler.HTTPSampler2.sample(HTTPSampler2.java:512)
> >> >        at
> >> > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:554)
> >> >        at
> >> > org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:543)
> >> >        at 
> >> > org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:247)
> >> >        at java.lang.Thread.run(Thread.java:595)
> >> >
> >> > with nothing of interest in jmeter.log.
> >> >
> >> > - Korny
> >> >
> >> > On 4/5/2006, "sebb" <[EMAIL PROTECTED]> wrote:
> >> >
> >> > >OK, I think I've fixed it - if you would like to test the nightly
> >> > >build 2-1.20060405 and let me know if that works, that would be a
> >> > >great help.
> >> > >
> >> > >S.
> >> > >On 05/04/06, sebb <[EMAIL PROTECTED]> wrote:
> >> > >> On 05/04/06, Korny Sietsma <[EMAIL PROTECTED]> wrote:
> >> > >> >
> >> > >> > I don't have an Auth manager - I thought that was for authentication
> >> > >> > within target applications, not at the proxy level?
> >> > >>
> >> > >> Sorry, you're right - it is for server based authentication.
> >> > >>
> >> > >> > I tried adding one, with a variety of differnt URLs, and it made no
> >> > >> > difference.
> >> > >> > There are no unusual messages in jmeter.log - in fact none at all 
> >> > >> > between:
> >> > >> > 2006/04/05 09:52:15 INFO  - jmeter.threads.JMeterThread: Thread 
> >> > >> > Thread
> >> > >> > Group 1-1 started
> >> > >> > 2006/04/05 09:52:15 INFO  - jmeter.threads.JMeterThread: Thread 
> >> > >> > Thread
> >> > >> > Group 1-1 is done
> >> > >> >
> >> > >> > I am running Jmeter 2.1.1
> >> > >> >
> >> > >> > Note as I mentioned below that the normal http request works fine, 
> >> > >> > it's
> >> > >> > just the HttpClient one that isn't working.  Very strange.
> >> > >> >
> >> > >> > In case it helps, the Sampler Result is as follows:
> >> > >> > --------------------------------------------
> >> > >> > Load time: 0
> >> > >> > HTTP response code: 407
> >> > >> > HTTP response message: Proxy Authentication Required
> >> > >> >
> >> > >> > HTTP response headers:
> >> > >> > HTTP/1.1 407 Proxy Authentication Required
> >> > >> > Date: Tue, 04 Apr 2006 23:59:40 GMT
> >> > >> > Content-Length: 257
> >> > >> > Content-Type: text/html
> >> > >> > Server: NetCache appliance (NetApp/5.5R5D5)
> >> > >> > Proxy-Connection: close
> >> > >> > Proxy-Authenticate: Basic realm="Sensis Internet Access"
> >> > >> > --------------------------------------------
> >> > >> >
> >> > >> > - Korny
> >> > >> >
> >> > >> > On 4/4/2006, "sebb" <[EMAIL PROTECTED]> wrote:
> >> > >> >
> >> > >> > >That should work. Do you have an HTTP Auth Manager in the plan?
> >> > >> > >
> >> > >> > >Are there any messages in jmeter.log?
> >> > >> > >
> >> > >> > >Which version of JMeter?
> >> > >> > >
> >> > >> > >S.
> >> > >> > >On 04/04/06, Kornelis Sietsma <[EMAIL PROTECTED]> wrote:
> >> > >> > >> Hi - I can't find this anywhere in the docs...
> >> > >> > >> I want to use a HttpClient HTTP Request, using a proxy server 
> >> > >> > >> with
> >> > >> > >> username/password authentication.
> >> > >> > >> I'm running jmeter with the parameters "-H [host] -P [port] -u
> >> > >> > >> [username] -p [password]" as specified.
> >> > >>
> >> > >> Looks like the -u and -p command-line parameters are not being passed
> >> > >> to HttpClient.
> >> > >>
> >> > >> I need to look into how best to pass the information across.
> >> > >> Hopefully I can fix this shortly.
> >> > >>
> >> > >> > >> Whenever I use the HttpClient version of the Http Request 
> >> > >> > >> sampler I get:
> >> > >> > >>  407 Proxy Authentication Required
> >> > >> > >>
> >> > >> > >> If I use the original HTTP Request sampler, the proxy 
> >> > >> > >> authentication
> >> > >> > >> works fine - unfortunately I have a pile of tests using the new
> >> > >> > >> HttpClient one, and changing back to the old sampler will 
> >> > >> > >> require quite
> >> > >> > >> a bit of effort...
> >> > >> > >>
> >> > >> > >> Any thoughts?
> >> > >> > >>
> >> > >> > >> - Korny
> >> > >> > >>
> >> > >> > >> --
> >> > >> > >> Kornelis Sietsma e-mail: korny at my surname dot com
> >> > >> > >>
> >> > >> > >>
> >> > >> > >> ---------------------------------------------------------------------
> >> > >> > >> 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