mirror of
https://github.com/curl/curl.git
synced 2026-08-26 06:43:31 +03:00
parent
551baf7d64
commit
b042d5297d
26 changed files with 42 additions and 43 deletions
|
|
@ -347,7 +347,7 @@
|
|||
|
||||
1.17 Add support for IRIs
|
||||
|
||||
IRIs (RFC 3987) allow localized, non-ascii, names in the URL. To properly
|
||||
IRIs (RFC 3987) allow localized, non-ASCII, names in the URL. To properly
|
||||
support this, curl/libcurl would need to translate/encode the given input
|
||||
from the input string encoding into percent encoded output "over the wire".
|
||||
|
||||
|
|
@ -1234,7 +1234,7 @@
|
|||
|
||||
-J/--remote-header-name does not decode %-encoded filenames. RFC 6266 details
|
||||
how it should be done. The can of worm is basically that we have no charset
|
||||
handling in curl and ascii >=128 is a challenge for us. Not to mention that
|
||||
handling in curl and ASCII >=128 is a challenge for us. Not to mention that
|
||||
decoding also means that we need to check for nastiness that is attempted,
|
||||
like "../" sequences and the like. Probably everything to the left of any
|
||||
embedded slashes should be cut off.
|
||||
|
|
|
|||
|
|
@ -226,7 +226,7 @@ directory listing for the root / home directory is returned.
|
|||
FTP servers typically put the user in its "home directory" after login, which
|
||||
then differs between users. To explicitly specify the root directory of an FTP
|
||||
server, start the path with double slash `//` or `/%2f` (2F is the hexadecimal
|
||||
value of the ascii code for the slash).
|
||||
value of the ASCII code for the slash).
|
||||
|
||||
## FILE
|
||||
|
||||
|
|
|
|||
|
|
@ -128,7 +128,7 @@ int main(void)
|
|||
CURLcode res;
|
||||
struct data config;
|
||||
|
||||
config.trace_ascii = 1; /* enable ascii tracing */
|
||||
config.trace_ascii = 1; /* enable ASCII tracing */
|
||||
|
||||
curl = curl_easy_init();
|
||||
if(curl) {
|
||||
|
|
|
|||
|
|
@ -116,13 +116,13 @@ new the libcurl you are using is. You are however guaranteed to get a struct
|
|||
that you have a matching struct for in the header, as you tell libcurl your
|
||||
"age" with the input argument.
|
||||
|
||||
*version* is just an ascii string for the libcurl version.
|
||||
*version* is just an ASCII string for the libcurl version.
|
||||
|
||||
*version_num* is a 24 bit number created like this: \<8 bits major number\> |
|
||||
\<8 bits minor number\> | \<8 bits patch number\>. Version 7.9.8 is therefore
|
||||
returned as 0x070908.
|
||||
|
||||
*host* is an ascii string showing what host information that this libcurl
|
||||
*host* is an ASCII string showing what host information that this libcurl
|
||||
was built for. As discovered by a configure script or set by the build
|
||||
environment.
|
||||
|
||||
|
|
|
|||
|
|
@ -1255,7 +1255,7 @@ curl_mime_subparts(3). Once it has been
|
|||
bound to its parent multi-part, a nth-level multi-part belongs to it and
|
||||
should not be freed explicitly.
|
||||
|
||||
Email messages data is not supposed to be non-ascii and line length is
|
||||
Email messages data is not supposed to be non-ASCII and line length is
|
||||
limited: fortunately, some transfer encodings are defined by the standards to
|
||||
support the transmission of such incompatible data. Function
|
||||
curl_mime_encoder(3) tells a part that its source data must be encoded
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue