-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCR Not Sending Client Certificate when wrapping Requests #220
Comments
Seems likely that this is because we only forward certain values explicitly to the actual connection. Line 176 in 2ac3fa9
Line 251 in 2ac3fa9
We probably need to store the data coming in as args, kwargs there and pass it on appropriately. But thats all just a guess. |
@fxfitz You didn't happen to investigate this any further, did you? |
Sadly, no, I haven't. |
I'd like to write a test for this, but since this happens at the protocol layer I'm not sure how to assert that the certificate is included. |
The SSL also changed in py2.7+ to use SSLContext instead of as args to the HTTPConnection object. So this might be version-dependent. |
A lot of changes have happened to VCRpy since this ticket was opened. As this ticket has become stale and we have a lot of old tickets that need to be groomed, I'm closing this for now to make it easier to see what is still relevant. However if it is still needed, please feel free to re-open or create a new ticket. Thanks! 🙏 |
When using VCR and attempting to send a client certificate to a webserver (as seen below), VCR does not include the certificate in the packets being sent out.
This can be confirmed by looking at a Wireshark capture (screenshot). When the client presents the certificate, you can see the 'Certificates Length' is actually 0.
This works as expected when not using VCR.
The text was updated successfully, but these errors were encountered: