diff options
| author | Jeremy Lainé <jeremy.laine@m4x.org> | 2015-08-15 01:17:55 +0200 |
|---|---|---|
| committer | Jeremy Lainé <jeremy.laine@m4x.org> | 2015-08-15 01:17:55 +0200 |
| commit | c7edb89abbb38c432667de15181b4cee6f14577e (patch) | |
| tree | 942d5c2ff728375b6d6320c62b85dd98f8c4f2cf /examples/example_1_echoClient/example_1_echoClient.cpp | |
| parent | ad1cf20d2ad46099d4de8dbeda1db51e91efcd7a (diff) | |
| download | qxmpp-c7edb89abbb38c432667de15181b4cee6f14577e.tar.gz | |
correctly receive data immediately following a SOCKS5 message (closes #64)
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.
Diffstat (limited to 'examples/example_1_echoClient/example_1_echoClient.cpp')
0 files changed, 0 insertions, 0 deletions