1. 06 Feb, 2017 - 1 commit
  2. 27 Jan, 2017 - 1 commit
  3. 25 Jan, 2017 - 1 commit
  4. 19 Jan, 2017 - 1 commit
  5. 06 Jan, 2017 - 1 commit
  6. 04 Jan, 2017 - 1 commit
    • Aleksey Lysenko's avatar
      Fixed possible block clearing in QWebSocketDataProcessor::process method · 2eeee81b
      Aleksey Lysenko authored
      
      In QWebSocketDataProcessor::process() the signals text(binary)MessageReceived
      are emitted before clear() method. If signal handler blocks loop
      (for example, using QDialog::exec()), clear() will be called only after
      resuming loop. It may lead to the data corruption due to the fact that
      QWebSocketDataProcessor clearing won't be performed before the new data
      arrived.
      
      Task-number: QTBUG-55506
      Change-Id: Ib7016a91d3987dec7c1af977b17f86a53568c413
      Reviewed-by: default avatarTimur Pocheptsov <timur.pocheptsov@qt.io>
      2eeee81b
  7. 03 Jan, 2017 - 1 commit
  8. 16 Dec, 2016 - 1 commit
  9. 14 Dec, 2016 - 1 commit
    • Aleksey Lysenko's avatar
      Fixed QWebSocketServer::SslMode collision · a5c85e32
      Aleksey Lysenko authored
      
      Value of NonSecureMode enumerator depends on QT_NO_SSL. If Qt is built with
      QT_NO_SSL defined, NonSecureMode is equal to 0, otherwise it is equal to 1.
      It may lead to problem if user built app with libs where NonSecureMode = 0,
      but run it with libs where NonSecureMode = 1.
      
      [ChangeLog][QWebSocketServer] SslMode::NonSecure enumerator now always has
      the same value (1) regardless of SSL enabled or disabled.
      
      Task-number: QTBUG-56129
      Change-Id: If17137eff4b19015697c827a985ef89dd95a5611
      Reviewed-by: default avatarTimur Pocheptsov <timur.pocheptsov@qt.io>
      a5c85e32
  10. 13 Dec, 2016 - 2 commits
  11. 26 Nov, 2016 - 1 commit
  12. 24 Nov, 2016 - 1 commit
  13. 06 Nov, 2016 - 1 commit
  14. 04 Oct, 2016 - 1 commit
  15. 01 Oct, 2016 - 1 commit
  16. 30 Sep, 2016 - 1 commit
  17. 21 Sep, 2016 - 1 commit
  18. 17 Sep, 2016 - 1 commit
  19. 14 Sep, 2016 - 1 commit
  20. 07 Sep, 2016 - 1 commit
  21. 29 Aug, 2016 - 2 commits
  22. 23 Aug, 2016 - 1 commit
  23. 19 Aug, 2016 - 1 commit
  24. 12 Aug, 2016 - 1 commit
  25. 02 Aug, 2016 - 1 commit
  26. 01 Aug, 2016 - 1 commit
  27. 28 Jul, 2016 - 1 commit
  28. 20 Jun, 2016 - 1 commit
    • Oleksandr Tymoshenko's avatar
      Fixed erroneous detection of server disconnect condition · e66dcd51
      Oleksandr Tymoshenko authored
      
      QAbstractSocket::atEnd does not check actual connection state it
      only checks if data is ready to be read. Under some conditions
      (e.g.  slow network) data may not be available yet but it doesn't
      mean the server dropped connection. When more data comes FSM will
      pick it up and handle as expected. The right way to check disconnect
      is to check for actual socket state.
      
      Task-number: QTBUG-51069
      Change-Id: I17d7110fbefdba2d5378a71935ab5923f8c1bf3e
      Reviewed-by: default avatarThiago Macieira <thiago.macieira@intel.com>
      e66dcd51
  29. 16 Jun, 2016 - 2 commits
  30. 12 Jun, 2016 - 1 commit
  31. 08 Jun, 2016 - 1 commit
  32. 26 May, 2016 - 1 commit
  33. 24 May, 2016 - 1 commit
  34. 23 May, 2016 - 1 commit
  35. 19 May, 2016 - 2 commits
  36. 12 May, 2016 - 1 commit