1. 28 Sep, 2017 - 1 commit
  2. 15 Aug, 2017 - 1 commit
  3. 14 Aug, 2017 - 1 commit
  4. 19 Jul, 2017 - 1 commit
    • Sami Nurmenniemi's avatar
      Enable tests for boot2qt · b73b3f8a
      Sami Nurmenniemi authored
      Websocket tests for boot2qt were disabled with commit
      1a75da8d
      
      . The tests can
      be enabled since qtdeclarative now fallbacks to software
      renderer if OpenGL is not supported.
      
      Qemu still has missing syscall support so some tests need
      to be skipped if that condition is detected.
      
      Change-Id: I39dba91cb35cc17a9a9263c90a739cbf95efa582
      Reviewed-by: default avatarSimon Hausmann <simon.hausmann@qt.io>
      b73b3f8a
  5. 30 Jun, 2017 - 4 commits
  6. 23 Jun, 2017 - 1 commit
  7. 07 Jun, 2017 - 1 commit
  8. 31 May, 2017 - 2 commits
  9. 15 May, 2017 - 1 commit
  10. 10 May, 2017 - 1 commit
  11. 09 May, 2017 - 1 commit
  12. 05 May, 2017 - 1 commit
  13. 04 May, 2017 - 2 commits
  14. 03 May, 2017 - 1 commit
  15. 27 Apr, 2017 - 2 commits
  16. 10 Mar, 2017 - 1 commit
  17. 22 Feb, 2017 - 1 commit
  18. 06 Feb, 2017 - 1 commit
  19. 03 Feb, 2017 - 1 commit
  20. 02 Feb, 2017 - 1 commit
  21. 27 Jan, 2017 - 1 commit
  22. 26 Jan, 2017 - 1 commit
  23. 25 Jan, 2017 - 1 commit
  24. 19 Jan, 2017 - 1 commit
  25. 06 Jan, 2017 - 1 commit
  26. 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
  27. 03 Jan, 2017 - 1 commit
  28. 16 Dec, 2016 - 1 commit
  29. 15 Dec, 2016 - 1 commit
  30. 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
  31. 13 Dec, 2016 - 2 commits
  32. 26 Nov, 2016 - 1 commit
  33. 24 Nov, 2016 - 1 commit