My IE user agent is Mozilla/4.0, same as in test plan, I changed my FF agent to the same, but can not access the site there, interestingly, it's throwing the same exception as JMeter:
Secure Connection Failed SSL peer was unable to negotiate an acceptable set of security parameters. (Error code: ssl_error_handshake_failure_alert) On Mon, Dec 20, 2010 at 9:49 AM, sebb <[email protected]> wrote: > On 20 December 2010 17:40, Akash Pancholi <[email protected]> > wrote: > > Thanks for the replies. > > > > The webstie needs a certificate, I could access it all right manually in > IE, > > and execute the plan using BadBoy. The test plan was recorded with > BadBoy, > > and exported to Jmeter. > > > > I tried without certificate first, but got the same error. Protocol is > HTTPS > > and port 443. I simplified the test plan to only one request, but still > got > > the same error. > > > > The website can be accessed only in IE, does that matter? > > That depends on why the website requires IE. > It may be sufficient to change the User-Agent. > > Can you access the site in FireFox if you change FF's User-Agent to > look like IE? > > Does it make any difference if you use the HttpClient HTTP sampler? > > > On Mon, Dec 20, 2010 at 6:08 AM, sebb <[email protected]> wrote: > > > >> On 20 December 2010 07:25, Felix Frank <[email protected]> wrote: > >> >> 1. Imported my certificate to cacerts (import was successful and > Jmeter > >> did > >> >> prompt me for password while running the script). > >> > > >> > Adding your certificates to Jmeter is only important when recording > >> > using the HTTP Proxy, afaik. > >> > >> Certificates aren't needed by JMeter unless the website needs a > >> *client* certificate (which is quite rare). > >> Are you sure the site needs a client certificate? > >> > >> JMeter provides its own certificate for HTTPS recording by its proxy. > >> If you wish, you can add that to your browser cert. store - but that's > >> not recommended, because the JMeter certificate is not secure. > >> > >> >> 2. Added following to System.properties: > >> > > >> > It is usually not required to make any changes to the properties, > HTTPS > >> > is supposed to work out of the box. > >> > >> Yes. > >> > >> >> ssl.provider=com.sun.net.ssl.internal.ssl.Provider > >> >> > >> >> ssl.pkgs=com.sun.net.ssl.internal.www.protocol > >> >> > >> >> I'm using Jmeter 2.4 and jre1.6. Appreciate any help. > >> > > >> > To ensure basic functionality, make a test plan that consists of only > >> > one sampler, which accesses your application's homepage. > >> > >> Good advice. > >> > >> > Make sure to specify the correct protocol (HTTPS) and port (probably > >> 443). > >> > >> Port 443 is selected by default for HTTPS (and 80 is selected for HTTP) > >> > >> > HTH, > >> > Felix > >> > > >> > --------------------------------------------------------------------- > >> > 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] > >
