mirror of
https://github.com/curl/curl.git
synced 2024-11-27 05:50:21 +08:00
2d0aca3b92
sends the 220 response or otherwise is dead slow, libcurl will not acknowledge the connection timeout during that phase but only the "real" timeout - which may surprise users as it is probably considered to be the connect phase to most people. Brought up (and is being misunderstood) in: http://curl.haxx.se/bug/view.cgi?id=2844077 |
||
---|---|---|
.. | ||
examples | ||
libcurl | ||
.cvsignore | ||
BINDINGS | ||
BUGS | ||
CONTRIBUTE | ||
curl-config.1 | ||
curl.1 | ||
DISTRO-DILEMMA | ||
FAQ | ||
FEATURES | ||
HISTORY | ||
index.html | ||
INSTALL | ||
INSTALL.cmake | ||
INSTALL.devcpp | ||
INTERNALS | ||
KNOWN_BUGS | ||
LICENSE-MIXING | ||
Makefile.am | ||
MANUAL | ||
README.cmake | ||
README.netware | ||
README.win32 | ||
RESOURCES | ||
SSLCERTS | ||
THANKS | ||
TheArtOfHttpScripting | ||
TODO | ||
VERSIONS |
_ _ ____ _ ___| | | | _ \| | / __| | | | |_) | | | (__| |_| | _ <| |___ \___|\___/|_| \_\_____| README.win32 Read the README file first. Curl has been compiled, built and run on all sorts of Windows and win32 systems. While not being the main develop target, a fair share of curl users are win32-based. The unix-style man pages are tricky to read on windows, so therefore are all those pages converted to HTML as well as pdf, and included in the release archives. The main curl.1 man page is also "built-in" in the command line tool. Use a command line similar to this in order to extract a separate text file: curl -M >manual.txt Read the INSTALL file for instructions how to compile curl self.