Comment 30 for bug 1665151

I can confirm this behaviour on 2.4.37 on two servers. I'm using these directives, and TLSv1.0 is still available

SSLHonorCipherOrder on
        SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS !DES !IDEA !RC2"

SSLProtocol -All +TLSv1.1 +TLSv1.2

nmap --script ssl-enum-ciphers -p 443 xxx.xxx.xxx.xxx | grep TLSv
| TLSv1.0:
| TLSv1.1:
| TLSv1.2: