3c8c9b2779
Otherwise a NOOP operation would be performed which a) only returns a single line response and not a multiline response where -I needs to be used, and b) provides an inconsistent user experience compared to that of the POP3 and IMAP protocols. |
||
---|---|---|
.. | ||
examples | ||
libcurl | ||
.gitignore | ||
BINDINGS | ||
BUGS | ||
CONTRIBUTE | ||
DISTRO-DILEMMA | ||
FAQ | ||
FEATURES | ||
HISTORY | ||
HTTP-COOKIES | ||
INSTALL | ||
INSTALL.cmake | ||
INSTALL.devcpp | ||
INTERNALS | ||
KNOWN_BUGS | ||
LIBCURL-STRUCTS | ||
LICENSE-MIXING | ||
MAIL-ETIQUETTE | ||
MANUAL | ||
Makefile.am | ||
README.cmake | ||
README.netware | ||
README.win32 | ||
RESOURCES | ||
SECURITY | ||
SSLCERTS | ||
THANKS | ||
TODO | ||
TheArtOfHttpScripting | ||
VERSIONS | ||
curl-config.1 | ||
curl.1 | ||
index.html | ||
mk-ca-bundle.1 |
README.win32
_ _ ____ _ ___| | | | _ \| | / __| | | | |_) | | | (__| |_| | _ <| |___ \___|\___/|_| \_\_____| 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.