Skip to content

HTTPClient https request fails if no fingerprint is provided #2902

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

Closed
torntrousers opened this issue Jan 26, 2017 · 4 comments
Closed

HTTPClient https request fails if no fingerprint is provided #2902

torntrousers opened this issue Jan 26, 2017 · 4 comments

Comments

@torntrousers
Copy link
Contributor

As per the comment made after Issue 2197 was closed, it should be possible to use HTTPClient with an https url without a fingerprint.

@olileger
Copy link

+1
Having the same request turns me to use WiFiClientSecure with more work to do

@torntrousers torntrousers changed the title HTTPClinet https request fails if no fingerprint is provided HTTPClient https request fails if no fingerprint is provided Jan 31, 2017
@zolv
Copy link

zolv commented Feb 11, 2017

Hi. As I checked, this issue should be fixed some time ago (Is it the same? #1941) - looks like it works in 2.1.0 but later it doesn't and is still there in 2.3.0-rc2.
@olileger Can You send some code snippet how to rewrite HTTPClient into WiFiClientSecure?

@liebman
Copy link
Contributor

liebman commented Dec 13, 2017

This PR allows specifying '*' as the fingerprint to skip validation #3933

@devyte
Copy link
Collaborator

devyte commented Jul 12, 2018

Currently bearssl is integrated. Although still experimental, it is strongly advised to migrate to it, because axtls is planned for deprecation, and then retirement.
Closing this.

@devyte devyte closed this as completed Jul 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants