Hi,
Neil A. Hillard wrote:
I've performed a packet capture and see the following events:
o Squid connects, logs in and changes to the correct directory.
o Squid issues a PORT command (Active FTP connection).
o FTP server acknowledges with a 200.
o Squid issues LIST command
o FTP server establishes data connection to Squid (three-way handshake
successful).
o FTP server issues:
125 Data connection already open; transfer starting.
response
o Squid returns 502 Bad Gateway error to client within 2ms of the
previous response.
This would indicate that Squid isn't happy with the 125 response from
the FTP server. The following is the debug output from Squid:
2005/10/06 11:06:23| ftpParseControlReply: s = {125 Data connection
already open; transfer starting.
}
2005/10/06 11:06:23| 125 Data connection already open; transfer starting.
2005/10/06 11:06:23| ftpHandleControlReply: state=9, code=125
2005/10/06 11:06:23| This is ftpReadList
2005/10/06 11:06:23| commSetSelect: FD 95 type 1
2005/10/06 11:06:23| commSetTimeout: FD 83 timeout -1
2005/10/06 11:06:23| commSetTimeout: FD 95 timeout 900
2005/10/06 11:06:23| comm_poll: 1+0 FDs ready
2005/10/06 11:06:23| comm_poll: FD 95 ready for reading
2005/10/06 11:06:23| comm_select: slow FD 95 selected for reading
2005/10/06 11:06:23| ftpDataRead: FD 95, Read -1 bytes
2005/10/06 11:06:23| ftpDataRead: read error: (107) Transport endpoint
is not connected
2005/10/06 11:06:23| fwdFail: ERR_READ_ERROR "Bad Gateway"
ftp://username:[EMAIL PROTECTED]/path/
Apologies for following up my own post but I've had a quick trawl
through the source code and it would appear that having delay pools
configured in has a bearing on the code used. I don't know a huge
amount of C so I don't think I can get to the bottom of this problem.
I will endeavor to get 2.5stable10 up and running on my development
server and test with / without delay pools compiled in to see if this
bears any relation to the problem.
TIA,
Neil.
--
Neil Hillard [EMAIL PROTECTED]
Westland Helicopters Ltd. http://www.whl.co.uk/
Disclaimer: This message does not necessarily reflect the
views of Westland Helicopters Ltd.
