You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jmeter.apache.org by se...@apache.org on 2013/10/15 16:34:56 UTC
svn commit: r1532363 - /jmeter/trunk/xdocs/usermanual/component_reference.xml
Author: sebb
Date: Tue Oct 15 14:34:56 2013
New Revision: 1532363
URL: http://svn.apache.org/r1532363
Log:
Clarify
Modified:
jmeter/trunk/xdocs/usermanual/component_reference.xml
Modified: jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=1532363&r1=1532362&r2=1532363&view=diff
==============================================================================
--- jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jmeter/trunk/xdocs/usermanual/component_reference.xml Tue Oct 15 14:34:56 2013
@@ -5812,7 +5812,7 @@ This setting will also be needed when ru
<p>
As mentioned above, when run under Java 7, JMeter can generate certificates for each server.
For this to work smoothly, the root CA signing certificate used by JMeter needs to be trusted by the browser.
-The first time that the proxy is started, it will generate the certificates.
+The first time that the recorder is started, it will generate the certificates if necessary.
The root CA certificate is exported into a file with the name <code>ApacheJMeterTemporaryRootCA</code> in the current launch directory.
When the certificates have been set up, JMeter will show a dialog with the current certificate details.
At this point, the certificate can be imported into the browser, as per the instructions below.