Custom Query (8142 matches)
Results (187 - 189 of 8142)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#248 | CAsyncSocketEx::IOCtl() returns wrong result | |||
Description |
The return value of CAsyncSocketEx::IOCtl() should be inverted. CAsyncSocketEx::IOCtl() calls ioctlsocket() which returns 0 if success, and SOCKET_ERROR if not success. CAsyncSocketEx::IOCtl() therefore should return TRUE if ioctlsocket() returns 0. This is not the case at the moment. This causes problems in WindowProc() of AsyncSocketEx.cpp when processing the FD_READ event. A correct implementation of IOCtl() would be: BOOL CAsyncSocketEx::IOCtl( long lCommand, DWORD* lpArgument ) {
(m_SocketData.hSocket, lCommand, lpArgument)); } |
|||
#249 | Server: TransferSocket::OnSend missing a byte | |||
Description |
in case numsent < numread, the remainder of the buffer is copied to the beginning of the buffer. However, the code as it is, will miss one byte, due to the incorrect +1. This causes corrupt files on the receiving client. Isn't it possible to use memcpy? or is this a problem as the two ranges overlap? else if (numsent<numread) { This should not happen, but handle it in case it happens
to send the specified
it most certainly
} |
|||
#250 | Queue Processing does not respect retry settings | |||
Description |
Using v2.1.3a: Not using multiple connections. Reproduce:
Expected Results: New connection attempt under entered username/password should proceed, if the connection is not made, the client should attempt to reconnect x number of times after waiting for y seconds, as specified in the settings dialogue. Actual Results: New connection attempt under entered username/password.
IMMEDIATELY. Very frustrating for ftp servers with auto-ban after x number of failed connections. |