On Mon, 31 Oct 2011, Yang Tse wrote:

> For active FTP, custom commands NODATACONN, NODATACONN421 and NODATACONN425
> dont even start the data sockfilter so client gets no connection.

Unfortunately it seems to bail out a little too early to repeat the bug report
case properly.

The problem case as I understand it, is when we do STOR or RETR and first get:

  150 Binary ...

followed by

  425 Can't open data connection

on the control connection and nothing at all happens on the data connection.

I wrote up a test case I want to try NODATACONN425 with (see test1206 as
attached) and this returns the 425 error already after the 200 response sent
to EPRT and is thus treated as an error to TYPE in this case:

23:04:05.395267 * protocol connect phase DONE
23:04:05.405986 * DO phase starts
23:04:05.420597 > EPRT |1|127.0.0.1|47064|
23:04:05.421652 * FTP 0x47df4a8 state change from STOP to PORT
23:04:05.423384 < 200 Thanks for dropping by. We contact you later
23:04:05.424315 * Connect data stream actively
23:04:05.424903 * FTP 0x47df4a8 state change from PORT to STOP
23:04:05.425878 * DO phase is complete
23:04:05.427192 * DO-MORE phase starts
23:04:05.431165 > TYPE I
23:04:05.431980 * FTP 0x47df4a8 state change from STOP to RETR_TYPE
23:04:05.432821 < 425 Can't open data connection
23:04:05.435579 * Couldn't set desired mode

-- 
  / daniel.haxx.se

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html