Searched refs:encoded (Results 51 – 65 of 65) sorted by relevance
123
/curl/docs/libcurl/ |
H A D | curl_url_get.md | 85 non-ASCII bytes that otherwise gets percent-encoded. 88 encoded to make sure the hostname remains valid.
|
H A D | libcurl-tutorial.md | 367 them URL encoded, as %XX where XX is a two-digit hexadecimal number. 427 in the HTTP request, base64-encoded. This is insecure. 683 source using fread(). The transfer is be chunk-encoded since the data size is 1261 curl_mime_encoder(3) tells a part that its source data must be encoded 1263 If the part data you want to send is already encoded in such a scheme, do not 1271 alternative and a file attachment encoded in base64:
|
H A D | curl_formadd.md | 180 chunked encoded. (Option added in libcurl 7.18.2)
|
H A D | libcurl-security.md | 69 base64 encoded passwords fool you. They may not look readable at a first
|
/curl/lib/vtls/ |
H A D | vtls.c | 1020 char *encoded = NULL, *pinkeycopy, *begin_pos, *end_pos; in Curl_pin_peer_pubkey() local 1037 CURL_SHA256_DIGEST_LENGTH, &encoded, in Curl_pin_peer_pubkey() 1044 infof(data, " public key hash: sha256//%s", encoded); in Curl_pin_peer_pubkey() 1049 Curl_safefree(encoded); in Curl_pin_peer_pubkey() 1065 !memcmp(encoded, begin_pos + 8, encodedlen)) { in Curl_pin_peer_pubkey() 1079 Curl_safefree(encoded); in Curl_pin_peer_pubkey()
|
/curl/tests/data/ |
H A D | test1123 | 178 HTTP GET deflate transfer-encoded content
|
/curl/docs/libcurl/opts/ |
H A D | CURLOPT_DEBUGFUNCTION.md | 79 data is encoded or compressed, it is not provided decoded nor decompressed
|
H A D | CURLOPT_SSH_KEYFUNCTION.md | 42 const char *key; /* points to a null-terminated string encoded with
|
H A D | CURLOPT_HEADERFUNCTION.md | 79 When a server sends a chunked encoded transfer, it may contain a trailer. That
|
H A D | CURLOPT_URL.md | 37 char * to a null-terminated string which must be URL-encoded in the following
|
/curl/docs/ |
H A D | KNOWN_BUGS | 270 UTF-8 encoded paths for internal use such as open, access and stat. The 272 not as UTF-8 encoded Unicode. 279 If a URL or filename cannot be encoded using the user's current codepage then 280 it can only be encoded properly in the Unicode character set. Windows uses
|
H A D | TODO | 171 18.27 -J and -O with %-encoded filenames 343 perhaps URL encoded byte values over 128 etc (basically do what the redirect 352 from the input string encoding into percent encoded output "over the wire". 1234 18.27 -J and -O with %-encoded filenames 1236 -J/--remote-header-name does not decode %-encoded filenames. RFC 6266 details 1244 -O also does not decode %-encoded names, and while it has even less
|
H A D | FAQ | 698 There are two ways. The way defined in the RFC is to use an encoded slash
|
/curl/docs/cmdline-opts/ |
H A D | form.md | 132 Data can be encoded for transfer using encoder=. Available encodings are
|
/curl/packages/OS400/ |
H A D | README.OS400 | 194 non-ccsid version and return a string encoded in the additional ccsid
|
Completed in 34 milliseconds
123