1. 21 Mar, 2014 - 1 commit
  2. 19 Mar, 2014 - 2 commits
  3. 18 Mar, 2014 - 1 commit
  4. 17 Mar, 2014 - 1 commit
  5. 14 Mar, 2014 - 3 commits
  6. 12 Mar, 2014 - 4 commits
  7. 11 Mar, 2014 - 3 commits
  8. 10 Mar, 2014 - 1 commit
  9. 01 Mar, 2014 - 4 commits
  10. 24 Feb, 2014 - 1 commit
  11. 16 Feb, 2014 - 5 commits
  12. 15 Feb, 2014 - 3 commits
  13. 13 Feb, 2014 - 2 commits
  14. 11 Feb, 2014 - 4 commits
  15. 09 Feb, 2014 - 1 commit
  16. 07 Feb, 2014 - 2 commits
  17. 06 Feb, 2014 - 2 commits
    • Milian Wolff's avatar
      Fix tst_QWebSocket::tst_invalidOpen for catch-all DNS setups. · 35a09924
      Milian Wolff authored
      
      Instead of relying on a hostname which might still be resolved in
      some DNS setups (i.e. always forward to google search or intranet),
      we now try to connect to localhost port 1 which should yield a
      ConnectionRefusedError.
      
      This way, the test passes for me on my setup.
      
      Change-Id: I025824796e94e718a42c4999706f647a72b37659
      Reviewed-by: default avatarKurt Pattyn <pattyn.kurt@gmail.com>
      35a09924
    • Milian Wolff's avatar
      Do not double-delete the TCP socket of a QWebSocket. · daf0faa0
      Milian Wolff authored
      
      The socket is put into an owning QScopedPointer. But if its also
      put into the QObject parent-child chain, it will get deleted when
      the QWebSocket is destroyed. In the dtor of the QWebSocketPrivate
      class m_pSocket will thus already be destroyed and thus be a
      dangling pointer.
      
      This crashed the QWebSocketServer test reliably for me on exit.
      
      Change-Id: I7f06e933bfed832e66b943542c351cde639c9465
      Reviewed-by: default avatarKurt Pattyn <pattyn.kurt@gmail.com>
      daf0faa0