Client-side SSL - HostnameVerificationPolicy.STRICT shouldn't accept wildcard certificates

HostnameVerificationPolicy.STRICT accepts wildcard certificates. Actually, it has exact same effect as HostnameVerificationPolicy.WILDCARD, because of this

switch (that.getHostnameVerification())
         {
            case ANY:
               verifier = new NoopHostnameVerifier();
               break;
            case WILDCARD:
               verifier = new DefaultHostnameVerifier();
               break;
            case STRICT:
               verifier = new DefaultHostnameVerifier();
               break;
          }

There should be different verifiers used in case of WILDCARD and STRICT.

See my test. Server is secured with wildcard certificate for hostname "*host" (wildcard for localhost) and HostnameVerificationPolicy.STRICT is used. Exception should be thrown but it isn't.