aboutsummaryrefslogtreecommitdiff
path: root/tests/qxmppsocks/tst_qxmppsocks.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Reformat codeLinus Jahn2022-09-061-1/+2
|
* Convert copyright headers to REUSELinus Jahn2022-01-141-22/+3
|
* Update copyright years (2022 edition)Linus Jahn2022-01-091-1/+1
|
* Update copyright headers to 2021Linus Jahn2021-02-191-1/+1
|
* Run clang-format also on all cpp filesLinus Jahn2020-02-031-2/+2
|
* clang-format: Enable regrouping and sorting of includesLinus Jahn2020-02-031-2/+3
|
* Port majority of old-style connects (#237)JBB2020-01-201-11/+11
| | | This provides more type safety and is future-proof.
* Bump copyright year to 2020Linus Jahn2020-01-061-1/+1
|
* Modernize codebase using clang-tidyJonah Brüchert2019-09-081-1/+1
| | | | | | | | Using the following checks: * modernize-use-nullptr * modernize-use-override * modernize-use-using * modernize-use-bool-literals
* Bump copyright year to 2019Jeremy Lainé2019-01-081-1/+1
|
* correctly receive data immediately following a SOCKS5 message (closes #64)Jeremy Lainé2015-08-151-3/+15
| | | | | | | | | | The SOCKS5 client and server would discard any currently buffered received data when processing a SOCKS5 command as they used readAll(). Now they only consume the SOCKS5 command's bytes, preserving any buffered data. Why this situation should occur is a different matter, I would be surprised to see it happen during file transfer, due to the sequence in which the handshake is performed.
* socks5: make server explicitly return "no acceptable method"Jeremy Lainé2015-07-271-0/+5
|
* socks5: improve test coverage of failed CONNECTJeremy Lainé2015-07-271-6/+33
|
* socks5: add test case for clientJeremy Lainé2015-07-271-45/+99
|
* improve testsJeremy Lainé2015-07-271-2/+15
|
* add some tests for invalid SOCKS5 handshake from clientJeremy Lainé2015-07-271-0/+45
|
* don't hardcode port 1080Jeremy Lainé2015-07-271-2/+1
|
* add some tests for QXmppSocksServerJeremy Lainé2015-07-271-0/+122