https://bz.apache.org/bugzilla/show_bug.cgi?id=60733
Maverick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- OS| |All --- Comment #1 from Maverick <[email protected]> --- Application uses The connection to this site uses a strong protocol (TLS 1.2), an obsolete key exchange (RSA), and a strong cipher (AES_128_GCM). And my JMeter Property file settings is #--------------------------------------------------------------------------- # SSL configuration #--------------------------------------------------------------------------- ## SSL System properties are now in system.properties # JMeter no longer converts javax.xxx property entries in this file into System properties. # These must now be defined in the system.properties file or on the command-line. # The system.properties file gives more flexibility. # By default, SSL session contexts are now created per-thread, rather than being shared. # 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 # List of protocols to enable. You may have to select only a subset if you find issues with target server. # This is needed when server does not support Socket version negotiation, this can lead to: # javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated # java.net.SocketException: Connection reset # see https://issues.apache.org/bugzilla/show_bug.cgi?id=54759 #https.socket.protocols=SSLv2Hello SSLv3 TLSv1 # Control if we allow reuse of cached SSL context between iterations # set the value to 'false' to reset the SSL context each iteration #https.use.cached.ssl.context=true -- You are receiving this mail because: You are the assignee for the bug.
