Yes, the transfered data is still sent encrypted. -k
/--insecure
will “only make” curl
skip certificate validation, it will not turn off SSL all together.
More information regarding the matter is available under the following link:
More Related Contents:
- SSL Error: unable to get local issuer certificate
- With HTTPS, are the URL and the request headers protected as the request body is?
- cURL requires CURLOPT_SSL_VERIFYPEER=FALSE
- How to redirect all HTTP requests to HTTPS
- Java: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
- curl: (60) SSL certificate problem: unable to get local issuer certificate
- Are querystring parameters secure in HTTPS (HTTP + SSL)? [duplicate]
- How to fix the “java.security.cert.CertificateException: No subject alternative names present” error?
- Will web browsers cache content over https
- Security consequences of disabling CURLOPT_SSL_VERIFYHOST (libcurl/openssl)
- Are HTTPS headers encrypted?
- SSL and man-in-the-middle misunderstanding
- A problem occurred somewhere in the SSL/TLS handshake
- Python requests SSL error – certificate verify failed
- How do I restore a missing IIS Express SSL Certificate?
- Use self signed certificate with cURL?
- PHP CURL CURLOPT_SSL_VERIFYPEER ignored
- Username and password in https url
- How to force java server to accept only tls 1.2 and reject tls 1.0 and tls 1.1 connections
- Get angular-cli to ng serve over HTTPS
- If you use HTTPS will your URL params will be safe from sniffing? [duplicate]
- Should I hash the password before sending it to the server side?
- https URL with token parameter : how secure is it?
- Is it secure to submit from a HTTP form to HTTPS?
- Is HTTP header Referer sent when going to a http page from a https page?
- NSURLConnection/CFURLConnection HTTP load failed (kCFStreamErrorDomainSSL, -9813) iOS
- How to redirect all HTTP requests to HTTPS using .htaccess rules?
- WS on HTTP vs WSS on HTTPS
- Why not use HTTPS for everything?
- Keygen tag in HTML5