You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using a self-signed certificate in development (local testing only) via a basic Git HTTPS server in Node.js.
I see that the option to skip the certificate check was removed in d2bdd34 — has anything changed since then? How do we support skipping the cert check (ala git config --global http.sslVerify false via CLI) in Objective-Git?
(“We need to re-enable it” is a valid response but I didn’t want to do that without having a chat about it.) :)
Update: I made the development server run over HTTP to avoid the issue. Would be nice to know what the recommended flow is for self-signed certs for the future though (I’d like to keep the dev/production environments as close as possible.)
The text was updated successfully, but these errors were encountered:
I’m using a self-signed certificate in development (local testing only) via a basic Git HTTPS server in Node.js.
I see that the option to skip the certificate check was removed in d2bdd34 — has anything changed since then? How do we support skipping the cert check (ala
git config --global http.sslVerify false
via CLI) in Objective-Git?(“We need to re-enable it” is a valid response but I didn’t want to do that without having a chat about it.) :)
Update: I made the development server run over HTTP to avoid the issue. Would be nice to know what the recommended flow is for self-signed certs for the future though (I’d like to keep the dev/production environments as close as possible.)
The text was updated successfully, but these errors were encountered: