You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rustls has support for the standard SSL key logging approach (useful when using Wireshark to analyze packet traces. However, hyper-rustls never configures the relevant field. As a result, it is very difficult to debug certain kinds of problems when TLS is in use. Would it be possible to expose this functionality, either by default or through the config builders? Thanks!
There is a From<(H, C)>impl for HttpsConnector that should be able to facilitate this use case. If you'd like a more ergonomic solution, we'd be open to a ConfigBuilderExt method for enabling KeyLogFile.
Thus far, the workaround is working for me. It would be nice if it was integrated natively into the ConfigBuilderExt, but it's definitely not critical.
We decided we don't want to expose this API more than necessary, and it should already be necessary to use the functionality by converting an existing ClientConfig into a HttpsConnector as described above. Going to close this issue.
Activity
djc commentedon Sep 11, 2024
There is a
From<(H, C)>implforHttpsConnectorthat should be able to facilitate this use case. If you'd like a more ergonomic solution, we'd be open to aConfigBuilderExtmethod for enablingKeyLogFile.cpu commentedon Sep 17, 2024
@pcd1193182 Would you be interested in writing a PR for this, or is the workaround described above sufficient for your needs?
pcd1193182 commentedon Sep 17, 2024
Thus far, the workaround is working for me. It would be nice if it was integrated natively into the ConfigBuilderExt, but it's definitely not critical.
graves commentedon Sep 7, 2025
This looked useful and like a simple addition so I implemented opened a PR here: #308
djc commentedon Sep 10, 2025
We decided we don't want to expose this API more than necessary, and it should already be necessary to use the functionality by converting an existing
ClientConfiginto aHttpsConnectoras described above. Going to close this issue.