Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Certificates & shared connection #45

Open
jweir opened this issue Jun 27, 2013 · 2 comments
Open

Certificates & shared connection #45

jweir opened this issue Jun 27, 2013 · 2 comments
Labels
Bug

Comments

@jweir
Copy link

jweir commented Jun 27, 2013

Should net-http-persistent not share connections for instances with different certificates?

I got burned by this using Mechanize. I know a solution is to name each instance, which works. But is that the following a principle of least surprise?

Related issue in Mechanize sparklemotion/mechanize#324
@drbrain
Copy link
Owner

drbrain commented Jul 24, 2013

To implement this properly you would need to tell net-http-persistent which hostnames a certificate was usable for. I will think about what API to use.

@drbrain drbrain added the Bug label Feb 6, 2014
@konstantin-dzreev
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@drbrain @jweir @konstantin-dzreev