usr/bin/ftp default file type varies depending on server

[dinplant]

The standard ftp client (usr/bin/ftp) default file type varies depending on which ftp server I connect to. For me this is strange since the TYPE is defined by the client, not the server.

scenarios:

SLES 9 ftp client connects to windows 3cdaemon server and the default type is binary.

SLES 9 ftp client connects to windows filezilla server and the default type is ascii.

*same windows server is used only the ftp server runnning is changed

[ab@novell.com]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That the client can specify ascii or binary is apparent but I do not
believe that overrides the possibility of the server having a default.
Doing a quick LAN trace of an FTP connection I do not see anything about
the transfer type in there by default.

Good luck.





dinplant wrote:
> The standard ftp client (usr/bin/ftp) default file type varies depending
> on which ftp server I connect to. For me this is strange since the TYPE
> is defined by the client, not the server.
>
> scenarios:
>
> SLES 9 ftp client connects to windows 3cdaemon server and the default
> type is binary.
>
> SLES 9 ftp client connects to windows filezilla server and the default
> type is ascii.
>
> *same windows server is used only the ftp server runnning is changed
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJK9B2iAAoJEF+XTK08PnB5NNQP+gJz5tbMca YuAB1Rm9Q+snuU
b/K98OG4n7XZii8rWlhP0h95p5j4dYeU5db/U2k7pKb3uJFhqH0Gqp34nSzV9WLk
Fs3Dz68Paib38yBpKLaWcM/97j7bBy+PMAtRvcFZ6MYcWpxfB57r6Z/lggSSJuUC
j+gg+xrDdNeZD3qBRgslqEhXD1kxS0fsAmZ4Lu7EkAMwUwv42i fSbpNebGHGwU1X
lAwCYEHskSV5BdL8kxn/6gAwhYBaFbBaAMMA8lngDvv3QuS7W+6v9x9AtthZ+eHd
D3wiiBQPvxO2SUIzsl+E1ljIMWVFQLRFZOdrn0jFZ6yZYrY5l4 n+QWJgt+Gq7Sha
lOeqBbQGeGFFcIsu+ln7V6cWRrLyQTexWYQ52WRVHa15UvdcN2 HiCbQ334Sdqj3n
7vbce9ZX2r8Ju58u39grgvx0FxqmAuRmOWK0/gtcjhCDGWyBgRSQDRH/NxOGjBEN
1+pV0uahscdFKQmi2KDREdCXZUXEkuxFUDQnswOByuSaac66Ab oAzOhj0cxjrgcA
aTSYj1fGIA29giArq3ziqqSGlH0dwM4CLg3LUC3oxoqwPs7shX cmopGRjB17aIpc
fbrlMqO1o3qHhoLhlpTCZa7Po+tfFi8ruKZrr3QQW2YN+RHRfD Ku8UCynRiampxj
OuCj/GRG7pdM4xmMX/VT
=Hl2M
-----END PGP SIGNATURE-----

[hcvv]

Often the 'default' type is dependent on the type of systems on both sites. I have seen systems (especialy of the Unix/Linux) type that have ASCII as default, but revert to BIN as default when they find out that the other system is of the same type.

This is because in that case a binary transfer works also perfect on ASCII type files and has better performance.

When systems are of a different type conversions like CR-LF to LF and vv. and ASCII to EBSDIC and vv. must possibly be done which is cared for by the ASCII type and thus this is taken as the default.

The above means that imho it is not so fixed what happens here. It is the outcome of some negotiation.

In any case I can only comment on the general case. I have no knowledge whatever about the MS software. Nor do I have more initimate knowlegde on the SLES distribution here in the openSUSE Forums.

[ken_yap]

It's not actually a file type but a transfer mode. As the default transfer mode is not mandated by any standard different servers do whatever they think might be the best for their users but in any case the client can explicitly request a transfer mode. It might also be possible that a server can detect the client OS and choose what they think is a good default. To be sure of the result, do not rely on any defaults.

[floydrodery]

The server can specify/negotiate the transfer type during the client/server connection.

You can change your transfer method via the GUI, or via command line.