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 POST is failing with certificate error #25

Closed
irfanazam1 opened this issue Jul 8, 2020 · 9 comments · Fixed by #66 or #70
Closed

HTTPS POST is failing with certificate error #25

irfanazam1 opened this issue Jul 8, 2020 · 9 comments · Fixed by #66 or #70
Assignees
Labels
willfixsoon Will try to fix soon

Comments

@irfanazam1
Copy link

I am trying to do a POST on an HTTPS address but getting the following error whereas the certificate has been imported into the ca-trusts as well in the browser.

failed, reason: self signed certificate in certificate chain

Kindly let me know if there is way to bypass certificate validation or where to import the certificate to resolve the issue.

Operating system: CentOS 7

@spluxx spluxx mentioned this issue Jul 27, 2020
@spluxx
Copy link
Owner

spluxx commented Jul 27, 2020

node-fetch/node-fetch#19 (comment)

It's a quick (and kinda unsafe) workaround, but I think it'll do. What do you think? I'll work on it next week.

@spluxx spluxx added the willfixsoon Will try to fix soon label Jul 27, 2020
@spluxx spluxx self-assigned this Jul 27, 2020
@irfanazam1
Copy link
Author

This is what I did and recompiled to make it working. It is unsafe but the tool is mostly used during dev/testing, so safety won't matter much.

@spluxx
Copy link
Owner

spluxx commented Jul 30, 2020

Nice. I'll address this on the next version. Thank you!

@wgithu
Copy link

wgithu commented May 14, 2021

Hi. When you have time, would you release a version with the fix for issue #25 in order to bypass certificate verification?

@irfanazam1
Copy link
Author

irfanazam1 commented May 15, 2021 via email

@dscmbvnc
Copy link

Hello. Will there be a new build with fix for issue #25 please?

@irfanazam1
Copy link
Author

irfanazam1 commented Jun 13, 2021 via email

@karan6190
Copy link

Hi team, is issue #25 resolved?

@vorte
Copy link
Contributor

vorte commented Sep 7, 2021

I've just raised a pr ^ which should resolve this issue. We just need to get it merged and released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
willfixsoon Will try to fix soon
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants