| Age | Commit message (Collapse) | Author | 
|---|
|  | to properly work with SOCKS5 proxies. I also included some ascii art describing
the SOCKS5 response, as RFC1928 describes. Jeff provided details in bug
report #741841 and here: http://curl.haxx.se/mail/lib-2004-02/0181.html | 
|  |  | 
|  | seems to correct some host cache screw-ups I could reproduce. | 
|  |  | 
|  | SO_BINDTODEVICE is present, to prevent compiler warnings about the variable | 
|  |  | 
|  |  | 
|  |  | 
|  | Removed some dates/names in the comments. | 
|  |  | 
|  |  | 
|  | Curl_write in CURLcode, to keep the picky compilers happy | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | more" when the previous approach. Known to work on Linux, possibly on other
platforms as well. | 
|  |  | 
|  |  | 
|  |  | 
|  | sure this doesn't get weird on 64bit archs. | 
|  |  | 
|  | archs, also no longer typecast pointers to ints as that is a nono on 64bit
systems. | 
|  |  | 
|  | a man page to text is found, we disable the built-in manual stuff to still
be able to build. | 
|  |  | 
|  |  | 
|  |  | 
|  | outside the source dir, not needing any symlinks | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | with anyway and thus caused picky compiler to warn. | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | we seem to have nailed that one now! | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  |