On 17/06/2009, Stromas, Aaron (NIH/OD) [C] <[email protected]> wrote: > There is no HTTP proxy, AFAIK. The Firebug shows that the initial request is > redirected (HTTP code 302) to a different HTTP port on that same server where > POST to /sso/auth occurs. > But now I noticed that "JMeter proxy server (see below) does not support > recording SSL (https)". It's only highlighted, after all :-). So, I reckon, I > need to hand code the test plan, right? >
Yes, just that part of the plan. > -a > > > -----Original Message----- > From: Noel O'Brien [mailto:[email protected]] > Sent: Wednesday, June 17, 2009 9:54 AM > To: JMeter Users List > Subject: Re: HTTP Proxy > > Are you behind a proxy? (i.e. the original request would have hit a proxy if > the JMeter proxy was not in place) > > I had a similar issue recently where all the traffic was HTTP but the > requests were trying to connect to a site proxy and the JMeter proxy cannot > handle the request to connect to it (i.e. CONNECT) > > Regards, > Noel > > ----- "Aaron Stromas (NIH/OD) [C]" <[email protected]> wrote: > > Well, the log suggests that HTTPS is used, although the Firebug shows HTTP > > > > 2009/06/17 09:25:35 ERROR - jmeter.protocol.http.proxy.Proxy: Not > implemented (probably used https) java.lang.IllegalArgumentException: Cannot > handle CONNECT - probably used HTTPS > > > > I'm confused about the item 2.2.4 SSL Encryption, though. The JDK 1.4.2 > I'm using (yes, this place is still on 1.4) has the crypto providers > installed: > > > > security.provider.1=sun.security.provider.Sun > > security.provider.2=com.sun.net.ssl.internal.ssl.Provider > > security.provider.3=com.sun.rsajca.Provider > > security.provider.4=com.sun.crypto.provider.SunJCE > > security.provider.5=sun.security.jgss.SunProvider > > > > So, what else is needed? > > > > -a > > > > -----Original Message----- > > From: sebb [mailto:[email protected]] > > Sent: Wednesday, June 17, 2009 9:19 AM > > To: JMeter Users List > > Subject: Re: HTTP Proxy > > > > Yes, the jmeter log created whilst running the proxy. > > > > On 17/06/2009, Stromas, Aaron (NIH/OD) [C] <[email protected]> wrote: > > > You mean to check the log while running the proxy, right? > > > > > > > > > -a > > > > > > -----Original Message----- > > > From: sebb [mailto:[email protected]] > > > > > > Sent: Wednesday, June 17, 2009 8:43 AM > > > To: JMeter Users List > > > Subject: Re: HTTP Proxy > > > > > > In that case, check the jmeter.log file for errors. > > > > > > If the browser sends the POST request to JMeter, it will generate a > > > sampler, and then use the sampler to generate the request and the > > > reply to the browser. > > > > > > On 17/06/2009, Stromas, Aaron (NIH/OD) [C] <[email protected]> wrote: > > > > No, it's HTTP. I double checked to be sure. > > > > > > > > -a > > > > > > > > > > > > -----Original Message----- > > > > From: sebb [mailto:[email protected]] > > > > Sent: Wednesday, June 17, 2009 8:31 AM > > > > To: JMeter Users List > > > > Subject: Re: HTTP Proxy > > > > > > > > On 17/06/2009, Stromas, Aaron (NIH/OD) [C] <[email protected]> > wrote: > > > > > Greetings, > > > > > > > > > > There is something that baffles me about the test plan obtained > using the JMeter HTTP proxy. I've "recorded" a test that includes SSO login, > i.e., submitting username/password. When I follow the scenario using Firefox > Firebug plugin I see a POST request, as expected. However, the recorded test > plan shows only GET requests. And the test plan executes! Can someone suggest > an explanation? I'd be most grateful. > > > > > > > > > > > > > Is the POST request http or https? > > > > If the latter, JMeter cannot record it, and won't even see it unless > > > > the browser proxy is set up to use JMeter for https. > > > > > > > > > -a > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > -- > Regards, > Noel > > > --------------------------------------------------------------------- > > 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]
