The servers I've encountered have all been part of the Sterling Commerce
CONNECT product. Sterling's software is very popular for electronic
commerce/EDI systems. Such commercial software products often carry a
legacy with it, and are not particularly up-to-date. The fact that it has
the 227 PASV/NAT firewall clash is likely viewed by Sterling as an asset,
since they sell an FTPS client that handles the problem. By adding
FTP_IGNORE_PASSIVE_IP, curl can be used instead of having to purchase a
commercial client that has none of the programmability of curl.

Saying "Just make sure your server supports EPSV" clearly demonstrates a
lack of understanding of the situation. IT'S NOT MY SERVER!!!!!

Ed Hingsbergen

|---------+--------------------------------->
| | Daniel Stenberg |
| | <daniel-curl_at_haxx.se> |
| | Sent by: |
| | curl-library-bounces_at_c|
| | ool.haxx.se |
| | |
| | |
| | 10/05/2004 06:45 AM |
| | Please respond to |
| | libcurl development |
| | |
|---------+--------------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
  | |
  | To: libcurl development <curl-library_at_cool.haxx.se> |
  | cc: |
  | Subject: Re: FTP_IGNORE_PASSIV_IP |
>------------------------------------------------------------------------------------------------------------------------------|

On Fri, 24 Sep 2004, Jamie Lokier wrote:

> Just make sure your server supports EPSV (modern replacement for PASV).
This
> don't have an IP address - just the port number.
>
> Any modern client should support EPSV. I believe Curl does.

I consider this the best response and cure for this problem.

Ed, you have any idea why these servers don't do this already?

--
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html