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
When using the requestTls option (specifically rejectUnauthorized) in conjunction with the DNS interceptor (interceptors.dns()), multiple SSL errors are thrown. The behavior changes depending on the configuration:
If I remove .compose([interceptors.dns()]), the issue disappears, and everything works fine.
If I remove requestTls completely, it also works fine even with .compose([interceptors.dns()]).
If I keep requestTls but remove only rejectUnauthorized: true (just { requestTls: {} } ), the error persists when .compose([interceptors.dns()]) is used.
This suggests an interaction between requestTls and the DNS interceptor that causes SSL issues.
This issue occurs whether requestTls is { rejectUnauthorized: true } or simply {}. It appears the combination of requestTls and interceptors.dns() triggers unexpected behavior.
Dumped connection info using MITMProxy
The text was updated successfully, but these errors were encountered:
Bug Description
When using the
requestTls
option (specificallyrejectUnauthorized
) in conjunction with the DNS interceptor (interceptors.dns()
), multiple SSL errors are thrown. The behavior changes depending on the configuration:.compose([interceptors.dns()])
, the issue disappears, and everything works fine.requestTls
completely, it also works fine even with.compose([interceptors.dns()])
.requestTls
but remove onlyrejectUnauthorized: true
(just{ requestTls: {} }
), the error persists when.compose([interceptors.dns()])
is used.This suggests an interaction between
requestTls
and the DNS interceptor that causes SSL issues.Reproducible By
Example 1: (issue)
Result:
Example two: (issue)
Result:
Click me to show large log
Expected Behavior
The request should succeed without SSL errors when using requestTls and the DNS interceptor together.
Environment
Ubuntu 22.04.5 LTS x86_64
v20.12.2
undici 7.2.0
Additional context
Maybe regression #3817 #3437
This issue occurs whether
requestTls
is{ rejectUnauthorized: true }
or simply{}
. It appears the combination ofrequestTls
andinterceptors.dns()
triggers unexpected behavior.Dumped connection info using MITMProxy
The text was updated successfully, but these errors were encountered: