Problem

ProxySQL incorrectly reports empty Ssl_version when clients execute SHOW STATUS LIKE 'ssl_version' to verify TLS connections, despite the client-ProxySQL connection being TLS-encrypted.

Cause

• ProxySQL forwards all SHOW STATUS queries to backends
• Backend connections are unencrypted, by default.
• The response reflects backend connection status, not client connection status

Proposed Solution

Intercept and handle SHOW STATUS LIKE 'ssl_version' directly in ProxySQL, returning the actual TLS version used for the client connection.