From: Daniel Stenberg <daniel@haxx.se>
Date: Wed, 14 Dec 2022 12:56:42 +0000 (+0100)
Subject: ssl-reqd.d: clarify that this is for upgrading connections only
X-Git-Tag: curl-7_87_0~15
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=50750d097aa55864498d2622fd14aad17fda941e;p=thirdparty%2Fcurl.git

ssl-reqd.d: clarify that this is for upgrading connections only

Closes #10093
---

diff --git a/docs/cmdline-opts/ssl-reqd.d b/docs/cmdline-opts/ssl-reqd.d
index cf81fb2291..6f95d5b672 100644
--- a/docs/cmdline-opts/ssl-reqd.d
+++ b/docs/cmdline-opts/ssl-reqd.d
@@ -9,11 +9,15 @@ Example: --ssl-reqd ftp://example.com
 See-also: ssl insecure
 Multi: boolean
 ---
-Require SSL/TLS for the connection. Terminates the connection if the server
-does not support SSL/TLS.
+Require SSL/TLS for the connection. Terminates the connection if the transfer
+cannot be upgraded to use SSL/TLS.
 
 This option is handled in LDAP since version 7.81.0. It is fully supported
 by the OpenLDAP backend and rejected by the generic ldap backend if explicit
 TLS is required.
 
+This option is unnecessary if you use a URL scheme that in itself implies
+immediate and implicit use of TLS, like for FTPS, IMAPS, POP3S, SMTPS and
+LDAPS. Such transfers will always fail if the TLS handshake does not work.
+
 This option was formerly known as --ftp-ssl-reqd.