Skip to content
  1. Jan 20, 2008
  2. Jan 18, 2008
  3. Jan 17, 2008
  4. Jan 16, 2008
  5. Jan 15, 2008
  6. Jan 14, 2008
  7. Jan 12, 2008
  8. Jan 11, 2008
  9. Jan 10, 2008
  10. Jan 08, 2008
  11. Jan 06, 2008
  12. Jan 05, 2008
  13. Jan 04, 2008
  14. Jan 02, 2008
    • Daniel Stenberg's avatar
      I removed the socklen_t use from the public curl/curl.h header and instead · 193d33fd
      Daniel Stenberg authored
      made it an unsigned int. The type was only used in the curl_sockaddr struct
      definition (only used by the curl_opensocket_callback). On all platforms I
      could find information about, socklen_t is 32 unsigned bits large so I don't
      think this will break the API or ABI. The main reason for this change is of
      course for all the platforms that don't have a socklen_t definition in their
      headers to build fine again. Providing our own configure magic and custom
      definition of socklen_t on those systems proved to work but was a lot of
      cruft, code and extra magic needed - when this very small change of type seems
      harmless and still solves the missing socklen_t problem.
      193d33fd
    • Daniel Stenberg's avatar
      Richard Atterer brought a patch that added support for SOCKS4a proxies, which · a46b40b7
      Daniel Stenberg authored
      is an inofficial PROXY4 variant that sends the hostname to the proxy instead
      of the resolved address (which is already supported by SOCKS5).  --socks4a is
      the curl command line option for it and CURLOPT_PROXYTYPE can now be set to
      CURLPROXY_SOCKS4A as well.
      a46b40b7
  15. Jan 01, 2008
  16. Dec 26, 2007
  17. Dec 24, 2007
  18. Dec 18, 2007
  19. Dec 17, 2007
  20. Dec 13, 2007
    • Daniel Stenberg's avatar
      David Wright filed bug report #1849764 · 7b1a2214
      Daniel Stenberg authored
      (http://curl.haxx.se/bug/view.cgi?id=1849764) with an included fix. He
      identified a problem for re-used connections that previously had sent
      Expect: 100-continue and in some situations the subsequent POST (that didn't
      use Expect:) still had the internal flag set for its use. David's fix (that
      makes the setting of the flag in every single request unconditionally) is
      fine and is now used!
      7b1a2214
  21. Dec 12, 2007
  22. Dec 09, 2007
  23. Dec 05, 2007
  24. Dec 03, 2007
  25. Dec 02, 2007
  26. Nov 29, 2007
  27. Nov 22, 2007
  28. Nov 20, 2007