From 95ddbdb1dbfbb051d67bf0d6643b1a917a4c7d88 Mon Sep 17 00:00:00 2001 From: Dan Fandrich Date: Mon, 14 Nov 2011 14:03:31 -0800 Subject: curl_easy_setopt arguments should be of type long in the examples --- docs/examples/smtp-tls.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/examples/smtp-tls.c') diff --git a/docs/examples/smtp-tls.c b/docs/examples/smtp-tls.c index 2e71f973e..8e2603fa4 100644 --- a/docs/examples/smtp-tls.c +++ b/docs/examples/smtp-tls.c @@ -94,13 +94,13 @@ int main(void) * of using CURLUSESSL_TRY here, because if TLS upgrade fails, the transfer * will continue anyway - see the security discussion in the libcurl * tutorial for more details. */ - curl_easy_setopt(curl, CURLOPT_USE_SSL, CURLUSESSL_ALL); + curl_easy_setopt(curl, CURLOPT_USE_SSL, (long)CURLUSESSL_ALL); /* If your server doesn't have a valid certificate, then you can disable * part of the Transport Layer Security protection by setting the * CURLOPT_SSL_VERIFYPEER and CURLOPT_SSL_VERIFYHOST options to 0 (false). - * curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 0); - * curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0); + * curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 0L); + * curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0L); * That is, in general, a bad idea. It is still better than sending your * authentication details in plain text though. * Instead, you should get the issuer certificate (or the host certificate @@ -135,7 +135,7 @@ int main(void) /* Since the traffic will be encrypted, it is very useful to turn on debug * information within libcurl to see what is happening during the transfer. */ - curl_easy_setopt(curl, CURLOPT_VERBOSE, 1); + curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L); /* send the message (including headers) */ res = curl_easy_perform(curl); -- cgit v1.2.3