You are viewing a plain text version of this content. The canonical link for it is here.
Posted to devnull@infra.apache.org by vl...@apache.org on 2019/06/08 18:42:08 UTC
[jmeter] 04/47: Document https.default.protocol
This is an automated email from the ASF dual-hosted git repository.
vladimirsitnikov pushed a commit to annotated tag v2_3
in repository https://gitbox.apache.org/repos/asf/jmeter.git
commit f35e90e8b836d090e7f4cd44fed6fb7619ee8e3a
Author: Sebastian Bazley <se...@apache.org>
AuthorDate: Wed Sep 12 15:10:29 2007 +0000
Document https.default.protocol
git-svn-id: https://svn.apache.org/repos/asf/jakarta/jmeter/branches/rel-2-2@574986 13f79535-47bb-0310-9956-ffa450edef68
Former-commit-id: 6d48e56d5ea4aa79026c87b42bc824ef9bbd31a0
---
bin/jmeter.properties | 5 +++++
xdocs/usermanual/component_reference.xml | 7 +++++++
xdocs/usermanual/get-started.xml | 8 ++++++--
3 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/bin/jmeter.properties b/bin/jmeter.properties
index 940add9..a25d9c5 100644
--- a/bin/jmeter.properties
+++ b/bin/jmeter.properties
@@ -61,6 +61,11 @@ xml.parser=org.apache.xerces.parsers.SAXParser
# The original behaviour can be enabled by setting the JMeter property:
#https.sessioncontext.shared=true
+# Default HTTPS protocol level:
+#https.default.protocol=TLS
+# This may need to be changed here (or in user.properties) to:
+#https.default.protocol=SSLv3
+
#---------------------------------------------------------------------------
# Look and Feel configuration
#---------------------------------------------------------------------------
diff --git a/xdocs/usermanual/component_reference.xml b/xdocs/usermanual/component_reference.xml
index cbc8db3..6f3dafe 100644
--- a/xdocs/usermanual/component_reference.xml
+++ b/xdocs/usermanual/component_reference.xml
@@ -136,6 +136,13 @@ JMeter assumes the FTP server is listening on the default port.</property>
https.sessioncontext.shared=true
</pre>
</p>
+ <p>
+ JMeter defaults to the SSL protocol level TLS.
+ If the server needs a different level, e.g. SSLv3, change the JMeter property, for example:
+<pre>
+https.default.protocol=SSLv3
+</pre>
+ </p>
<p>If the request uses cookies, then you will also need an
<complink name="HTTP Cookie Manager"/>. You can
add either of these elements to the Thread Group or the HTTP Request. If you have
diff --git a/xdocs/usermanual/get-started.xml b/xdocs/usermanual/get-started.xml
index b0ad289..25e771b 100644
--- a/xdocs/usermanual/get-started.xml
+++ b/xdocs/usermanual/get-started.xml
@@ -122,8 +122,12 @@ To enable Email support, add Sun's JavaMail packages and the activation packages
<p>To test a web server using SSL encryption (HTTPS), JMeter requires that an
implementation of SSL be provided, as is the case with Sun Java 1.4 and above.
If your version of Java does not include SSL support, then it is possible to add an external implementation.
-Include the necessary encryption packages in JMeter's <a href="#classpath">classpath</a>. Also, update <a href="#configuring_jmeter">jmeter.properties</a>
-to register the SSL Provider.</p>
+Include the necessary encryption packages in JMeter's <a href="#classpath">classpath</a>.
+Also, update <a href="#configuring_jmeter">system.properties</a> to register the SSL Provider.</p>
+<p>
+JMeter defaults to protocol level TLS. This can be changed by editting the JMeter property
+"https.default.protocol" in jmeter.properties or user.properties.
+</p>
<p><b>JMeter is configured to accept all certificates,
whether trusted or not, regardless of validity periods etc.</b>
This is to allow the maximum flexibility in testing servers.</p>