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.
securityguy
All 4 comments
axTLS now has support for SNI, so we can expose this feature via WiFiClientSecure.
igrr
on 29 Feb 2016
👍1
Heh. Just got same problem and ticket already is here =).
doom369
on 19 Mar 2016
👍1
So umm, dunno about you but SNI is still not sent, how can I force it?
emilfihlman
on 5 Jul 2017
👍3
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
kotfarepra
on 30 Dec 2017
👍1
Was this page helpful?
0 / 5 - 0 ratings
Related issues
pablotix20
路
3Comments
dariopb
路
3Comments
eliabieri
路
3Comments
Chagui-
路
3Comments
mechanic98
路
3Comments
Most helpful comment
So umm, dunno about you but SNI is still not sent, how can I force it?