Skip to content
  1. Sep 04, 2018
  2. Sep 03, 2018
  3. Aug 29, 2018
  4. Aug 27, 2018
  5. Aug 25, 2018
  6. Aug 24, 2018
  7. Aug 23, 2018
    • Daniel Stenberg's avatar
      libcurl-thread.3: expand somewhat on the NO_SIGNAL motivation · 1b8ed4ad
      Daniel Stenberg authored
      Multi-threaded applictions basically MUST set CURLOPT_NO_SIGNAL to 1L to
      avoid the risk of getting a SIGPIPE.
      
      Either way, a multi-threaded application that uses libcurl/openssl needs
      to have a signhandler for or ignore SIGPIPE on its own.
      
      Based on discussions in #2800
      Closes #2904
      1b8ed4ad
  8. Aug 21, 2018
  9. Aug 20, 2018
  10. Aug 15, 2018
  11. Aug 13, 2018
  12. Aug 11, 2018
  13. Aug 10, 2018
  14. Aug 09, 2018
  15. Aug 08, 2018
    • Anderson Toshiyuki Sasaki's avatar
      ssl: set engine implicitly when a PKCS#11 URI is provided · 298d2565
      Anderson Toshiyuki Sasaki authored
      This allows the use of PKCS#11 URI for certificates and keys without
      setting the corresponding type as "ENG" and the engine as "pkcs11"
      explicitly. If a PKCS#11 URI is provided for certificate, key,
      proxy_certificate or proxy_key, the corresponding type is set as "ENG"
      if not provided and the engine is set to "pkcs11" if not provided.
      
      Acked-by: Nikos Mavrogiannopoulos
      Closes #2333
      298d2565
  16. Aug 03, 2018
  17. Jul 29, 2018
  18. Jul 28, 2018
  19. Jul 26, 2018
    • Darío Hereñú's avatar
      docs/INSTALL.md: minor formatting fixes · 7212c4cd
      Darío Hereñú authored
      Closes #2794
      7212c4cd
    • Christopher Head's avatar
      docs/CURLOPT_URL: fix indentation · 812d05da
      Christopher Head authored
      The statement, “The application does not have to keep the string around
      after setting this option,” appears to be indented under the RTMP
      paragraph. It actually applies to all protocols, not just RTMP.
      Eliminate the extra indentation.
      
      Closes #2788
      812d05da
    • Christopher Head's avatar
      docs/CURLOPT_WRITEFUNCTION: size is always 1 · 9526cbe6
      Christopher Head authored
      For compatibility with `fwrite`, the `CURLOPT_WRITEFUNCTION` callback is
      passed two `size_t` parameters which, when multiplied, designate the
      number of bytes of data passed in. In practice, CURL always sets the
      first parameter (`size`) to 1.
      
      This practice is also enshrined in documentation and cannot be changed
      in future. The documentation states that the default callback is
      `fwrite`, which means `fwrite` must be a suitable function for this
      purpose. However, the documentation also states that the callback must
      return the number of *bytes* it successfully handled, whereas ISO C
      `fwrite` returns the number of items (each of size `size`) which it
      wrote. The only way these numbers can be equal is if `size` is 1.
      
      Since `size` is 1 and can never be changed in future anyway, document
      that fact explicitly and let users rely on it.
      
      Closes #2787
      9526cbe6
  20. Jul 14, 2018
  21. Jul 12, 2018
  22. Jul 11, 2018
  23. Jul 10, 2018
  24. Jul 09, 2018
  25. Jul 06, 2018
  26. Jul 05, 2018
  27. Jul 02, 2018