On Wed, 28 Jun 2000, you wrote:
> YES!!!! That fixed it. Now, if I had only asked you first instead of all
> those other people<g>....
Good :). A word of explanation to everyone about this:
FTP can be used in the following ways:
- active mode, no proxy. (This is the default)
- passive mode, no proxy.
- active mode, SOCKS5.
- passive mode, SOCKS5.
- passive mode, SOCKS4.
Note that the SOCKS4 protocol does not support incoming connections, so the
combination "active mode, SOCKS4" is not possible.
Up until REBOL/Core 2.2 "passive mode" would only be used if REBOL detected
that "active mode" does not work with a user's setup (automatic fallback). This
fallback still exists in Core 2.3, but experience shows that not all FTP
servers support the automatic fallback (in particular FTP servers on Win-NT
often do not support it because they do not detect "connection refused"
errors), and sometimes SOCKS servers have problems with the fallback as well.
As a workaround for these server bugs Core 2.3 also allows users to manually
switch to passive mode by putting
system/schemes/ftp/passive: true
into user.r. That forces FTP to always use passive mode.
One other enhancement in the FTP implementation from Core 2.2 to 2.3 was that
Core 2.3 supports "active mode, SOCKS5". Core 2.2 did not support this,
i.e. it always fell back to passive mode when SOCKS5 was used for FTP, which
caused problems for some users. Core 2.3 now supports all possible combinations
of proxy servers and active/passive modes for FTP.
--
Holger Kruse
[EMAIL PROTECTED]
