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

Allow unsecure https connections #22

Open
fabiobento512 opened this issue May 18, 2021 · 5 comments
Open

Allow unsecure https connections #22

fabiobento512 opened this issue May 18, 2021 · 5 comments
Labels
feature new feature request

Comments

@fabiobento512
Copy link
Owner

A new option should be added so FRequest allows unsecure http requests. This is useful for self signed certificate connections.

@fabiobento512 fabiobento512 added the feature new feature request label May 18, 2021
@Dean-NC
Copy link

Dean-NC commented May 28, 2021

Version 1.1c already works fine for me accessing my localhost with http and https (self-signed cert created automatically by Visual Studio).
My sites are on localhost using ASP.Net with .Net 5, and https self-signed works fine in both IIS Express web server and Microsoft Kestrel server.

@Bizarrus
Copy link

Bizarrus commented Nov 7, 2023

By me, a selfsigned-cert breaks up with following error:
image

The cert was created by openssl:

openssl req -x509 -sha256 -days 356 -noenc -newkey rsa:2048 -subj "/CN=example1.fruit/O=fruithost/[email protected]" -keyout /ssl/example2.fruit.key -out /ssl/example2.fruit.cert

On Webbrowser, the cert will accepted after invalid-authority-acceptance.

@SalDaniele
Copy link

Is this still currently unsupported? I am encountering the same issue as Bizarrus, this would be very nice to have

@fabiobento512
Copy link
Owner Author

fabiobento512 commented Apr 22, 2024

Is this still currently unsupported? I am encountering the same issue as Bizarrus, this would be very nice to have

Yes unfortunately. My life has been complicated lately and I have not been able to implement some of these basic features.

I have not tested it, but it may be possible, as workaround to add temporarily your self-signed certificates as trusted in the operating system you are using (if you have permissions to do it), possibly with that you should not see the error anymore on FRequest.

@SalDaniele
Copy link

Yes I tried this but no luck, curl works fine but the tool still throws ssl complaints. Great tool otherwise, super easy to use / lightweight, thanks!

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

No branches or pull requests

4 participants