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.

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

HTTPS doesn't send SNI #1285

Closed
securityguy opened this issue Dec 22, 2015 · 4 comments
Closed

HTTPS doesn't send SNI #1285

securityguy opened this issue Dec 22, 2015 · 4 comments

Comments

@securityguy
Copy link

securityguy commented Dec 22, 2015

WiFiClientSecure doesn't appear to have the ability to send Server Name Indication (SNI), making it difficult to connect to SNI-enabled servers with multiple certificates.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@igrr igrr added this to the 2.2.0 milestone Feb 29, 2016
@igrr igrr self-assigned this Feb 29, 2016
@igrr
Copy link
Member

igrr commented Feb 29, 2016

axTLS now has support for SNI, so we can expose this feature via WiFiClientSecure.

@doom369
Copy link

doom369 commented Mar 19, 2016

Heh. Just got same problem and ticket already is here =).

@emilfihlman
Copy link

So umm, dunno about you but SNI is still not sent, how can I force it?

@diekaines
Copy link

Any news on this ? Im using to connect to some websites that has SNI enabled and HTTPS forced . Would be great if it didnt softreset for those

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants