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]
