1. 04 Sep, 2018 1 commit
  2. 03 Sep, 2018 1 commit
  3. 29 Aug, 2018 1 commit
  4. 27 Aug, 2018 3 commits
  5. 25 Aug, 2018 1 commit
  6. 24 Aug, 2018 1 commit
  7. 23 Aug, 2018 1 commit
    • 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. 21 Aug, 2018 2 commits
  9. 20 Aug, 2018 2 commits
  10. 15 Aug, 2018 1 commit
  11. 13 Aug, 2018 1 commit
  12. 11 Aug, 2018 1 commit
  13. 10 Aug, 2018 1 commit
  14. 09 Aug, 2018 1 commit
  15. 08 Aug, 2018 1 commit
    • 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. 03 Aug, 2018 1 commit
  17. 29 Jul, 2018 1 commit
  18. 28 Jul, 2018 2 commits
  19. 26 Jul, 2018 3 commits
    • 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. 14 Jul, 2018 1 commit
  21. 12 Jul, 2018 1 commit
  22. 11 Jul, 2018 2 commits
  23. 10 Jul, 2018 2 commits
  24. 09 Jul, 2018 1 commit
  25. 06 Jul, 2018 1 commit
  26. 05 Jul, 2018 2 commits
  27. 02 Jul, 2018 4 commits