2004-05-13 04:22:40 -04:00
|
|
|
/*****************************************************************************
|
2004-11-24 11:11:35 -05:00
|
|
|
* _ _ ____ _
|
|
|
|
* Project ___| | | | _ \| |
|
|
|
|
* / __| | | | |_) | |
|
|
|
|
* | (__| |_| | _ <| |___
|
2004-05-13 04:22:40 -04:00
|
|
|
* \___|\___/|_| \_\_____|
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <stdio.h>
|
|
|
|
#include <curl/curl.h>
|
|
|
|
|
|
|
|
int main(void)
|
|
|
|
{
|
|
|
|
CURL *curl;
|
|
|
|
CURLcode res;
|
|
|
|
|
|
|
|
curl = curl_easy_init();
|
|
|
|
if(curl) {
|
2010-10-05 09:00:19 -04:00
|
|
|
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com/");
|
2004-05-13 04:22:40 -04:00
|
|
|
|
|
|
|
#ifdef SKIP_PEER_VERIFICATION
|
|
|
|
/*
|
|
|
|
* If you want to connect to a site who isn't using a certificate that is
|
|
|
|
* signed by one of the certs in the CA bundle you have, you can skip the
|
|
|
|
* verification of the server's certificate. This makes the connection
|
|
|
|
* A LOT LESS SECURE.
|
|
|
|
*
|
|
|
|
* If you have a CA cert for the server stored someplace else than in the
|
|
|
|
* default bundle, then the CURLOPT_CAPATH option might come handy for
|
|
|
|
* you.
|
|
|
|
*/
|
2008-05-22 17:20:07 -04:00
|
|
|
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 0L);
|
2004-05-13 04:22:40 -04:00
|
|
|
#endif
|
|
|
|
|
|
|
|
#ifdef SKIP_HOSTNAME_VERFICATION
|
|
|
|
/*
|
|
|
|
* If the site you're connecting to uses a different host name that what
|
|
|
|
* they have mentioned in their server certificate's commonName (or
|
|
|
|
* subjectAltName) fields, libcurl will refuse to connect. You can skip
|
|
|
|
* this check, but this will make the connection less secure.
|
|
|
|
*/
|
2008-05-22 17:20:07 -04:00
|
|
|
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0L);
|
2004-05-13 04:22:40 -04:00
|
|
|
#endif
|
|
|
|
|
|
|
|
res = curl_easy_perform(curl);
|
|
|
|
|
|
|
|
/* always cleanup */
|
|
|
|
curl_easy_cleanup(curl);
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|