It is mostly superfluous. proselint would complain.
Closes #11818
HTTP/3 when you know that the target speaks HTTP/3 on the given host and port.
When asked to use HTTP/3, curl will issue a separate attempt to use older HTTP
-versions with a slight delay, so if the HTTP/3 transfer fails or is very slow,
-curl will still try to proceed with an older HTTP version.
+versions with a slight delay, so if the HTTP/3 transfer fails or is slow, curl
+will still try to proceed with an older HTTP version.
Use --http3-only for similar functionality *without* a fallback.
snprintf(nline, sizeof(nline), "%s\t%s\t%s\t%s\t%.0f\t%s\t%s",
".example.com", "TRUE", "/", "FALSE",
difftime(time(NULL) + 31337, (time_t)0),
- "PREF", "hello example, i like you very much!");
+ "PREF", "hello example, i like you!");
res = curl_easy_setopt(curl, CURLOPT_COOKIELIST, nline);
if(res != CURLE_OK) {
fprintf(stderr, "Curl curl_easy_setopt failed: %s\n",
rc = curl_multi_add_handle(g->multi, conn->easy);
mcode_or_die("new_conn: curl_multi_add_handle", rc);
- /* note that the add_handle() will set a time-out to trigger very soon so
- that the necessary socket_action() call will be called by this app */
+ /* note that the add_handle() will set a time-out to trigger soon so that
+ the necessary socket_action() call will be called by this app */
}
/* This gets called whenever data is received from the fifo */
rc = curl_multi_add_handle(g->multi, conn->easy);
mcode_or_die("new_conn: curl_multi_add_handle", rc);
- /* note that the add_handle() will set a time-out to trigger very soon so
- that the necessary socket_action() call will be called by this app */
+ /* note that the add_handle() will set a time-out to trigger soon so that
+ the necessary socket_action() call will be called by this app */
}
/* This gets called whenever data is received from the fifo */
rc = curl_multi_add_handle(g->multi, conn->easy);
mcode_or_die("new_conn: curl_multi_add_handle", rc);
- /* note that the add_handle() will set a time-out to trigger very soon so
- that the necessary socket_action() call will be called by this app */
+ /* note that the add_handle() will set a time-out to trigger soon so that
+ the necessary socket_action() call will be called by this app */
}
/* This gets called by glib whenever data is received from the fifo */
rc = curl_multi_add_handle(g->multi, conn->easy);
mcode_or_die("new_conn: curl_multi_add_handle", rc);
- /* note that the add_handle() will set a time-out to trigger very soon so
- that the necessary socket_action() call will be called by this app */
+ /* note that the add_handle() will set a time-out to trigger soon so that
+ the necessary socket_action() call will be called by this app */
}
/* This gets called whenever data is received from the fifo */
/* This is just the server URL */
curl_easy_setopt(curl, CURLOPT_URL, "imap://imap.example.com");
- /* Set the LSUB command. Note the syntax is very similar to that of a LIST
+ /* Set the LSUB command. Note the syntax is similar to that of a LIST
command. */
curl_easy_setopt(curl, CURLOPT_CUSTOMREQUEST, "LSUB \"\" *");
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0L);
#endif
- /* Since the traffic will be encrypted, it is very useful to turn on debug
+ /* Since the traffic will be encrypted, it is useful to turn on debug
* information within libcurl to see what is happening during the
* transfer */
curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L);
* for more information. */
curl_easy_setopt(curl, CURLOPT_CAINFO, "/path/to/certificate.pem");
- /* Since the traffic will be encrypted, it is very useful to turn on debug
+ /* Since the traffic will be encrypted, it is useful to turn on debug
* information within libcurl to see what is happening during the
* transfer */
curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L);
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 0L);
#endif
- /* Since the traffic will be encrypted, it is very useful to turn on debug
+ /* Since the traffic will be encrypted, it is useful to turn on debug
* information within libcurl to see what is happening during the
* transfer */
curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L);
* for more information. */
curl_easy_setopt(curl, CURLOPT_CAINFO, "/path/to/certificate.pem");
- /* Since the traffic will be encrypted, it is very useful to turn on debug
+ /* Since the traffic will be encrypted, it is useful to turn on debug
* information within libcurl to see what is happening during the
* transfer */
curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L);
*/
/* The libcurl options want plain addresses, the viewable headers in the mail
- * can very well get a full name as well.
+ * can get a full name as well.
*/
#define FROM_ADDR "<ursel@example.org>"
#define SENDER_ADDR "<kurt@example.org>"
* should be able to reuse this connection for additional messages
* (setting CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and
* calling curl_easy_perform() again. It may not be a good idea to keep
- * the connection open for a very long time though (more than a few
- * minutes may result in the server timing out the connection), and you do
- * want to clean up in the end.
+ * the connection open for a long time though (more than a few minutes may
+ * result in the server timing out the connection), and you do want to
+ * clean up in the end.
*/
curl_easy_cleanup(curl);
}
curl_slist_free_all(recipients);
/* curl will not send the QUIT command until you call cleanup, so you
- * should be able to reuse this connection for additional requests. It
- * may not be a good idea to keep the connection open for a very long time
- * though (more than a few minutes may result in the server timing out the
+ * should be able to reuse this connection for additional requests. It may
+ * not be a good idea to keep the connection open for a long time though
+ * (more than a few minutes may result in the server timing out the
* connection) and you do want to clean up in the end.
*/
curl_easy_cleanup(curl);
*/
/* The libcurl options want plain addresses, the viewable headers in the mail
- * can very well get a full name as well.
+ * can get a full name as well.
*/
#define FROM_ADDR "<sender@example.org>"
#define TO_ADDR "<addressee@example.net>"
* should be able to reuse this connection for additional messages
* (setting CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and
* calling curl_easy_perform() again. It may not be a good idea to keep
- * the connection open for a very long time though (more than a few
- * minutes may result in the server timing out the connection), and you do
- * want to clean up in the end.
+ * the connection open for a long time though (more than a few minutes may
+ * result in the server timing out the connection), and you do want to
+ * clean up in the end.
*/
curl_easy_cleanup(curl);
}
* should be able to reuse this connection for additional messages
* (setting CURLOPT_MAIL_FROM and CURLOPT_MAIL_RCPT as required, and
* calling curl_easy_perform() again. It may not be a good idea to keep
- * the connection open for a very long time though (more than a few
- * minutes may result in the server timing out the connection), and you do
- * want to clean up in the end.
+ * the connection open for a long time though (more than a few minutes may
+ * result in the server timing out the connection), and you do want to
+ * clean up in the end.
*/
curl_easy_cleanup(curl);
curl_easy_setopt(curl, CURLOPT_READDATA, &upload_ctx);
curl_easy_setopt(curl, CURLOPT_UPLOAD, 1L);
- /* Since the traffic will be encrypted, it is very useful to turn on debug
+ /* Since the traffic will be encrypted, it is useful to turn on debug
* information within libcurl to see what is happening during the
* transfer */
curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L);
curl_easy_setopt(curl, CURLOPT_READDATA, &upload_ctx);
curl_easy_setopt(curl, CURLOPT_UPLOAD, 1L);
- /* 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.
+ /* Since the traffic will be encrypted, it is useful to turn on debug
+ * information within libcurl to see what is happening during the
+ * transfer.
*/
curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L);
curl_slist_free_all(recipients);
/* curl will not send the QUIT command until you call cleanup, so you
- * should be able to reuse this connection for additional requests. It
- * may not be a good idea to keep the connection open for a very long time
- * though (more than a few minutes may result in the server timing out the
+ * should be able to reuse this connection for additional requests. It may
+ * not be a good idea to keep the connection open for a long time though
+ * (more than a few minutes may result in the server timing out the
* connection) and you do want to clean up in the end.
*/
curl_easy_cleanup(curl);
*
* Synchronising your computer clock via Internet time server usually relies
* on DAYTIME, TIME, or NTP protocols. These protocols provide good accurate
- * time synchronization but it does not work very well through a
+ * time synchronization but it does not work well through a
* firewall/proxy. Some adjustment has to be made to the firewall/proxy for
* these protocols to work properly.
*
* 2. Webserver system time must in sync with the NTP time server,
* or at least provide an accurate time keeping.
* 3. Webserver HTTP header does not provide the milliseconds units,
- * so there is no way to get very accurate time.
+ * so there is no way to get an accurate time.
* 4. This software could only provide an accuracy of +- a few seconds,
* as Round-Trip delay time is not taken into consideration.
* Compensation of network, firewall/proxy delay cannot be simply divide
input strings longer than \fBCURL_MAX_INPUT_LENGTH\fP (8 MB).
Since 7.82.0, the \fBcurl\fP parameter is ignored. Prior to that there was
-per-handle character conversion support for some very old operating systems
-such as TPF, but it was otherwise ignored.
+per-handle character conversion support for some old operating systems such as
+TPF, but it was otherwise ignored.
You must \fIcurl_free(3)\fP the returned string when you are done with it.
.SH ENCODING
this parameter.
Since 7.82.0, the \fBcurl\fP parameter is ignored. Prior to that there was
-per-handle character conversion support for some very old operating systems
-such as TPF, but it was otherwise ignored.
+per-handle character conversion support for some old operating systems such as
+TPF, but it was otherwise ignored.
You must \fIcurl_free(3)\fP the returned string when you are done with it.
.SH EXAMPLE
# Users may override the detected values by doing something like:
# LIBCURL="-lcurl" LIBCURL_CPPFLAGS="-I/usr/myinclude" ./configure
#
-# For the sake of sanity, this macro assumes that any libcurl that is
-# found is after version 7.7.2, the first version that included the
-# curl-config script. Note that it is very important for people
-# packaging binary versions of libcurl to include this script!
-# Without curl-config, we can only guess what protocols are available,
-# or use curl_version_info to figure it out at runtime.
+# For the sake of sanity, this macro assumes that any libcurl that is found is
+# after version 7.7.2, the first version that included the curl-config script.
+# Note that it is important for people packaging binary versions of libcurl to
+# include this script! Without curl-config, we can only guess what protocols
+# are available, or use curl_version_info to figure it out at runtime.
AC_DEFUN([LIBCURL_CHECK_CONFIG],
[
#
###########################################################################
#
-# Experience has shown that the symbols-in-versions file is very useful to
-# applications that want to build with a wide range of libcurl versions.
-# It is however easy to get it wrong and the source gets a bit messy with all
-# the fixed numerical comparisons.
+# Experience has shown that the symbols-in-versions file is useful to
+# applications that want to build with a wide range of libcurl versions. It
+# is however easy to get it wrong and the source gets a bit messy with all the
+# fixed numerical comparisons.
#
# The point of this script is to provide an easy-to-use macro for libcurl-
# using applications to do preprocessor checks for specific libcurl defines,
projects / thirdparty / curl.git / commitdiff
