mirror of
https://github.com/curl/curl.git
synced 2026-06-02 07:54:15 +03:00
parent
db02e0e980
commit
307b7543ea
19 changed files with 26 additions and 26 deletions
|
|
@ -59,8 +59,8 @@ Releases the previously referenced buffer, then duplicates the `length`-byte
|
|||
`data` into a buffer allocated via `malloc()` and references the latter
|
||||
associated with destructor `curl_free()`.
|
||||
|
||||
An additional trailing byte is allocated and set to zero as a possible
|
||||
string zero-terminator; it is not counted in the stored length.
|
||||
An additional trailing byte is allocated and set to zero as a possible string
|
||||
null-terminator; it is not counted in the stored length.
|
||||
|
||||
Returns `CURLE_OK` if successful, else `CURLE_OUT_OF_MEMORY`.
|
||||
|
||||
|
|
|
|||
|
|
@ -151,12 +151,12 @@ Maybe use of `realloc()` should rather use the dynbuf functions?
|
|||
Do not allow new code that grows buffers without using dynbuf.
|
||||
|
||||
Use of C functions that rely on a terminating zero must only be used on data
|
||||
that really do have a zero terminating zero.
|
||||
that really do have a null-terminating zero.
|
||||
|
||||
## Dangerous "data styles"
|
||||
|
||||
Make extra precautions and verify that memory buffers that need a terminating
|
||||
zero always have exactly that. Buffers *without* a zero terminator must not be
|
||||
zero always have exactly that. Buffers *without* a null-terminator must not be
|
||||
used as input to string functions.
|
||||
|
||||
# Commit messages
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ CURLHcode curl_easy_header(CURL *easy,
|
|||
.SH DESCRIPTION
|
||||
\fIcurl_easy_header(3)\fP returns a pointer to a "curl_header" struct in
|
||||
\fBhout\fP with data for the HTTP response header \fIname\fP. The case
|
||||
insensitive nul-terminated header name should be specified without colon.
|
||||
insensitive null-terminated header name should be specified without colon.
|
||||
|
||||
\fIindex\fP 0 means asking for the first instance of the header. If the
|
||||
returned header struct has \fBamount\fP set larger than 1, it means there are
|
||||
|
|
@ -94,7 +94,7 @@ but it might have a different case.
|
|||
|
||||
The data \fBvalue\fP field points to, comes exactly as delivered over the
|
||||
network but with leading and trailing whitespace and newlines stripped
|
||||
off. The `value` data is nul-terminated. For legacy HTTP/1 "folded headers",
|
||||
off. The `value` data is null-terminated. For legacy HTTP/1 "folded headers",
|
||||
this API provides the full single value in an unfolded manner with a single
|
||||
whitespace between the lines.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ typedef enum {
|
|||
CURLOT_VALUES, /* (a defined set or bitmask) */
|
||||
CURLOT_OFF_T, /* curl_off_t (a range of values) */
|
||||
CURLOT_OBJECT, /* pointer (void *) */
|
||||
CURLOT_STRING, /* (char * to zero terminated buffer) */
|
||||
CURLOT_STRING, /* (char * to null-terminated buffer) */
|
||||
CURLOT_SLIST, /* (struct curl_slist *) */
|
||||
CURLOT_CBPTR, /* (void * passed as-is to a callback) */
|
||||
CURLOT_BLOB, /* blob (struct curl_blob *) */
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ the POST data from the read callback. If you want to send a zero-byte POST set
|
|||
\fICURLOPT_POSTFIELDS(3)\fP to an empty string, or set \fICURLOPT_POST(3)\fP to
|
||||
1 and \fICURLOPT_POSTFIELDSIZE(3)\fP to 0.
|
||||
|
||||
libcurl will use assume this option points to a nul-terminated string unless
|
||||
libcurl will use assume this option points to a null-terminated string unless
|
||||
you also set \fICURLOPT_POSTFIELDSIZE(3)\fP to specify the length of the
|
||||
provided data, which then is strictly required if you want to send off nul
|
||||
bytes included in the data.
|
||||
|
|
|
|||
|
|
@ -59,12 +59,12 @@ The callback function must return \fICURL_PREREQFUNC_OK\fP on success, or
|
|||
|
||||
This function is passed the following arguments:
|
||||
.IP conn_primary_ip
|
||||
A nul-terminated pointer to a C string containing the primary IP of the remote
|
||||
server established with this connection. For FTP, this is the IP for the
|
||||
control connection. IPv6 addresses are represented without surrounding
|
||||
A null-terminated pointer to a C string containing the primary IP of the
|
||||
remote server established with this connection. For FTP, this is the IP for
|
||||
the control connection. IPv6 addresses are represented without surrounding
|
||||
brackets.
|
||||
.IP conn_local_ip
|
||||
A nul-terminated pointer to a C string containing the originating IP for this
|
||||
A null-terminated pointer to a C string containing the originating IP for this
|
||||
connection. IPv6 addresses are represented without surrounding brackets.
|
||||
.IP conn_primary_port
|
||||
The primary port number on the remote server established with this connection.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue