Feature #9758
closed
Allow setting SSLContext#extra_chain_cert in Net::HTTP
Added by stouset (Stephen Touset) over 10 years ago.
Updated over 4 years ago.
Description
Currently, Net::HTTP
can only send a single SSL certificate when it
establishes a connection. Some use-cases involve sending an entire
certificate chain to the destination; for this, SSLContext
supports
assigning to #extra_chain_cert=
.
This adds support in Net::HTTP
for exposing this underlying SSLContext
property to end-users.
Files
- Tracker changed from Bug to Feature
- Description updated (diff)
This change is still blocking X509 certificate presentation with Net::HTTP, specifically when an intermediate certificate is required. The current workaround is to create a mixin for the Net::HTTP module (see the blog post linked in the previous comment), but this isn't a great long term solution. Is there another, less hacky way to solve this?
This issue has been open for nearly 5 years. Other than the patch being outdated, is there a reason this hasn't been merged? I'm happy to update the patch and resubmit, if that's the only obstacle.
Thanks!
- Status changed from Open to Closed
Applied in changeset git|31af0dafba6d3769d2a39617c0dddedb97883712.
Expose SSLContext#extra_chain_cert in Net::HTTP
Currently, Net::HTTP can only send a single SSL certificate when it
establishes a connection. Some use-cases involve sending an entire
certificate chain to the destination; for this, SSLContext supports
assigning to #extra_chain_cert=.
This adds support in Net::HTTP for exposing this underlying SSLContext
property to end-users. [Feature #9758]
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0