Searched refs:client (Results 1776 – 1788 of 1788) sorted by relevance
1...<<7172
| /curl/tests/data/ |
| H A D | test442 | 33 <client>
199 </client>
|
| H A D | test1061 | 870 <client>
885 </client>
|
| H A D | test1060 | 865 <client>
880 </client>
|
| /curl/docs/libcurl/ |
| H A D | curl_easy_getinfo.md | 360 The RTSP client CSeq that is expected next.
|
| H A D | libcurl.md | 18 libcurl - client-side URL transfers
|
| H A D | libcurl-errors.md | 312 problem with the local client certificate.
|
| H A D | libcurl-tutorial.md | 423 different ways a client can provide those credentials to the server and you
1158 the name and value to the client, and expects it to get sent back on every
|
| /curl/docs/ |
| H A D | FAQ | 138 A client-side URL transfer library, supporting DICT, FILE, FTP, FTPS,
267 During the summer of 2001, curl.com was busy advertising their client-side
534 that informs the client about this is only interpreted if you are using the
667 does not require this, you do not need a client certificate.
669 A client certificate is always used together with a private key, and the
842 syntax. The client SHOULD NOT repeat the request without modifications.
1075 perfectly legal for the client to wait indefinitely for data, the stack may
1184 that DLL use the FILE * (as the DLL and the client application cannot access
1392 Internet protocol server. libcurl is only a client-side library. For server
|
| /curl/tests/http/testenv/ |
| H A D | env.py | 148 CertificateSpec(name="user1", client=True),
|
| /curl/lib/ |
| H A D | urldata.h | 417 Gsasl_session *client; member
|
| /curl/.github/workflows/ |
| H A D | linux.yml | 370 …RUSTFLAGS="--cfg hyper_unstable_ffi" cargo +nightly rustc --features client,http1,http2,ffi -Z uns…
|
| /curl/ |
| H A D | CMakeLists.txt | 1846 # Export a .pc file for client projects not using CMake
|
| H A D | configure.ac | 144 PKGADD_NAME="curl - a client that groks URLs"
|
Completed in 74 milliseconds
1...<<7172
