1. 15 Aug, 2018 1 commit
  2. 09 Aug, 2018 2 commits
  3. 27 May, 2018 1 commit
  4. 26 May, 2018 1 commit
  5. 22 May, 2018 1 commit
  6. 14 May, 2018 2 commits
    • Luca Boccassi's avatar
      Problem: ZMTP 3.1 PING Context not implemented · b331caad
      Luca Boccassi authored
      Solution: if a PING message contains a context, echo it back in the
      PONG message. In order to do so, create the PONG message when PING
      is received and store it in the engine.
      After the PING the engine goes straight to encoding and sending, so
      there can always be at most one pending PING.
      Add tests for various contexts.
      b331caad
    • Luca Boccassi's avatar
      Problem: heartbeat command parsing does not check command name size · 5482b1ca
      Luca Boccassi authored
      Solution: treat the first byte of the command body as the size of the
      command name, rather than as an id, to comply with ZMTP 3.1.
      This was not an actual problem at runtime since both heartbeat
      commands have a size of 4, which was treated like an id.
      But once SUBSCRIBE/UNSUBSCRIBE get implemented it needs to be checked.
      5482b1ca
  7. 08 Feb, 2018 1 commit
  8. 02 Feb, 2018 1 commit
  9. 19 Sep, 2017 1 commit
  10. 07 Sep, 2017 1 commit
  11. 06 Sep, 2017 1 commit
  12. 08 Aug, 2017 1 commit
    • Simon Giesecke's avatar
      Problem: ZAP status codes != 200 do not result in an appropriate monitor event (#2665) · a6cef4ef
      Simon Giesecke authored
      * Problem: missing test for status code 300, inadequate assertion for status code 500
      
      Solution: add test, change assertion (currently test fails)
      
      * Problem: gcc compiler error deprecated conversion from string constant
      
      Solution: declare variable as const
      
      * Problem: in case of ZAP handler returning a status code other than 200, no appropriate event is emitted
      
      Solution: immediately emit event after receiving reply from ZAP handler
      
      * Problem: endpoint address is not included in zap-reply monitor event
      
      Solution: added functions to retrieve endpoint address in zmq::i_engine and zmq::session_base_t
      removed unused code block in zmq::stream_engine_t::next_handshake_command
      
      * Problem: wrong formatting
      
      Solution: fix formatting
      
      * Problem: test fails because of EPIPE
      
      Solution: add EPIPE/ECONNRESET/ECONNAGAIN handling for more test cases
      a6cef4ef
  13. 01 Jan, 2017 1 commit
    • Vincent Tellier's avatar
      Fixed issue #2227 second part · ffb31dca
      Vincent Tellier authored
       - removed the previously added encryption_error, less changes less bug
       - handshake fail is now signaled when an error happen while the
         mechanism is still hanshaking
      ffb31dca
  14. 30 Dec, 2016 1 commit
    • Vincent Tellier's avatar
      Fixed issue #2227 · b6e9e0c2
      Vincent Tellier authored
      Added two new monitoring events:
       - ZMQ_EVENT_HANDSHAKE_SUCCEED is raised once the encryption handshake succeed
       - ZMQ_EVENT_HANDSHAKE_FAILED is raised when it failed
      Both events are raised on server and client side.
      b6e9e0c2
  15. 15 Dec, 2016 1 commit
  16. 14 May, 2016 1 commit
  17. 28 Jan, 2016 1 commit
  18. 26 Jun, 2015 1 commit
    • Jonathan Reams's avatar
      Fix units and default values for heartbeats options · e9a5bc8d
      Jonathan Reams authored
      Set the ZMQ_HEARTBEAT_TIMEOUT to default to the value of
      ZMQ_HEARTBEAT_IVL if it's not explicitly set.
      Change the units of ZMQ_HEARTBEAT_TTL to milliseconds in the API
      and round down to the nearest decisecond so that all the options
      are using the same units.
      Make the maximum heartbeat TTL match the spec (6553 seconds)
      e9a5bc8d
  19. 24 Jun, 2015 1 commit
  20. 02 Jun, 2015 1 commit
  21. 19 Feb, 2015 1 commit
  22. 18 Feb, 2015 1 commit
  23. 22 Jan, 2015 1 commit
  24. 09 Jan, 2015 1 commit
  25. 22 Jun, 2014 1 commit
    • Martin Hurton's avatar
      Add support for SOCKS proxies · f06ca69a
      Martin Hurton authored
      This is still raw and experimental.
      To connect through a SOCKS proxy, set ZMQ_SOCKS_PROXY socket option on
      socket before issuing a connect call, e.g.:
      
          zmq_setsockopt (s, ZMQ_SOCKS_PROXY,
              "127.0.0.1:22222", strlen ("127.0.0.1:22222"));
          zmq_connect (s, "tcp://127.0.0.1:5555");
      
      Known limitations:
      - only SOCKS version 5 supported
      - authentication not supported
      - new option is still undocumented
      f06ca69a
  26. 17 May, 2014 1 commit
  27. 09 May, 2014 1 commit
  28. 05 May, 2014 1 commit
  29. 02 May, 2014 1 commit
  30. 30 Apr, 2014 1 commit
  31. 12 Jan, 2014 1 commit
  32. 02 Jan, 2014 2 commits
  33. 07 Nov, 2013 1 commit
  34. 09 Oct, 2013 1 commit
  35. 04 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Updated libzmq to match RFC 23, 24, 25, 26 · 28b0a5fa
      Pieter Hintjens authored
      * Command names changed from null terminated to length-specified
      * Command frames use the correct flag (bit 2)
      * test_stream acts as test case for command frames
      * Some code cleanups
      28b0a5fa
  36. 18 Jul, 2013 1 commit
  37. 22 Jun, 2013 1 commit