Wlidcard matching is performed against proxy IP when using proxy about tlsdate HOT 1 CLOSED

% tlsdate -nvV -H encrypted.google.com -x http://127.0.0.1:8118
V: tlsdate version 0.0.6
V: We were called with the following arguments:
V: validate SSL certificates host = encrypted.google.com:443
V: time is currently 1365792099.296515247
V: time is greater than RECENT_COMPILE_DATE
V: using TLSv1_client_method()
V: Using OpenSSL for SSL
V: opening socket to 127.0.0.1:8118
V: certificate verification passed
V: commonName mismatch! Expected: encrypted.google.com - received: *.google.com
V: found non subjectAltName extension
V: found non subjectAltName extension
V: found non subjectAltName extension
V: found non subjectAltName extension
V: found non subjectAltName extension
V: found non subjectAltName extension
V: Inspecting 'encrypted.google.com' for possible wildcard match against '*.google.com'
V: label found; total label count: 1
V: label found; total label count: 2
V: label found; total label count: 3
V: Found wildcard in at start of provided certificate name
V: Attempting match of 'encrypted' against '*'
V: Forced match of 'encrypted' against '*'
V: Attempting match of 'google' against 'google'
V: Attempting match of 'com' against 'com'
V: remaining labels match!
V: wildcard match of encrypted.google.com against *.google.com
V: hostname verification passed
V: public key is ready for inspection
V: key type: EVP_PKEY_RSA
V: keybits: 1024
V: key length appears safe
V: server time 1365792180 (difference is about -81 s) was fetched in 4986 ms
V: the TLS handshake took more than 2000 msecs - consider using a different server or run it again
Fri Apr 12 11:43:00 PDT 2013