Description:
------------
---
From manual page: https://php.net/function.curl-setopt
---

As the title says, documentation for these two groups of macros is outdated. More recent documentation is here: https://curl.haxx.se/libcurl/c/CURLOPT_SSLVERSION.html I went to https://edit.php.net/ for bringing this up to date, saving gets accepted, but public documentation doesn't update. If there are additional steps required I'm not aware of them.

In case somebody with more privileges needs to apply this, here's the new row for CURLOPT_SSLVERSION in en/reference/curl/functions/curl-setopt.xml I came up with:

---
          <row>
           <entry valign="top"><constant>CURLOPT_SSLVERSION</constant></entry>
           <entry valign="top">
            Sets the minimum acceptable TLS version for the connection.
            <constant>CURL_SSLVERSION_DEFAULT</constant> (0),
            <constant>CURL_SSLVERSION_TLSv1</constant> (1),
            <constant>CURL_SSLVERSION_SSLv2</constant> (2),
            <constant>CURL_SSLVERSION_SSLv3</constant> (3),
            <constant>CURL_SSLVERSION_TLSv1_0</constant> (4),
            <constant>CURL_SSLVERSION_TLSv1_1</constant> (5) or
            <constant>CURL_SSLVERSION_TLSv1_2</constant> (6).
            The maximum TLS version used. It is also possible to OR one of the
            CURL_SSLVERSION_ macros with one of the CURL_SSLVERSION_MAX_ macros.
            Added in cURL 7.54.0.
            <constant>CURL_SSLVERSION_MAX_DEFAULT</constant> The maximum version
            supported by the library.
            <constant>CURL_SSLVERSION_MAX_TLSv1_0</constant>
            <constant>CURL_SSLVERSION_MAX_TLSv1_1</constant>
            <constant>CURL_SSLVERSION_MAX_TLSv1_2</constant>
            <constant>CURL_SSLVERSION_MAX_TLSv1_3</constant>
            <note>
             <para>
              Your best bet is to not set this and let it use the default.
             </para>
            </note>
           </entry>
           In versions of cURL prior to 7.54 the CURL_SSLVERSION_{SSL|TLS} options
           were documented to allow only the specified TLS version, but
           behavior was inconsistent depending on the TLS library.
          </row>
---