1. 19 Jan, 2017 6 commits
  2. 16 Jan, 2017 2 commits
  3. 12 Jan, 2017 2 commits
  4. 11 Jan, 2017 2 commits
  5. 10 Jan, 2017 3 commits
  6. 09 Jan, 2017 2 commits
  7. 08 Jan, 2017 1 commit
  8. 07 Jan, 2017 4 commits
  9. 06 Jan, 2017 5 commits
  10. 04 Jan, 2017 2 commits
    • Constantin Rack's avatar
      Merge pull request #2292 from bluca/osx_sigpipe · ceb6be77
      Constantin Rack authored
      Problem: peer can close connection before SO_NOSIGPIPE is set
      ceb6be77
    • Luca Boccassi's avatar
      Problem: peer can close connection before SO_NOSIGPIPE is set · 31a3a068
      Luca Boccassi authored
      Solution: setsockopt returns EINVAL if the connection was closed by
      the peer after the accept returned a valid socket. This is a valid
      network error and should not cause an assert.
      To handle this we have to extract the setsockopt from the stream
      engine, as there's no clean way to return an error from the
      constructor. Instead, try to set this option before creating the
      engine in the callers, and return immediately as if the accept
      had failed to avoid churn. Do the same for the connect calls by
      setting the option in open_socket, so that the option for that
      case is set even before connecting, so there's no possible race
      condition.
      Since this has to be done in 4 places (tcp/ipc listener, socks
      connecter and open_socket) add an utility function in ip.cpp.
      Fixes #1442
      31a3a068
  11. 03 Jan, 2017 6 commits
  12. 01 Jan, 2017 5 commits