On Thu, 24 Aug 2006, Armel Asselin wrote:

> from a functional point of view, the minimal work would be to:

[complex description cut out]

That is not what I'd call a "nice" way, no. It is a lot of (error-prone) code
for a very rare edge case with a broken server.

> if not putting that inside libcurl (and/or public libcurl), how could I put
> it outside?

I would say that you should have a header callback and scan for the PASV
responses and if you get a "bad" one you disconnect that easy handle and then
redo that connection.

Unless you can come up with a "nice" way to tell libcurl to restart a
connection (or even the FTP command/response chain) once you've detected the
badness.

> I could still keep the modifs for me, but it would be a hassle to merge :(

Of course, but the root of this evil is not libcurl and I don't see why we
should punish all existing libcurl users because of a single (very) bad server
implementation.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html