Difference between revisions of "Post login commands"

From FileZilla Wiki
Jump to navigationJump to search
m (This is an educational site, not a site where personal vendettas against a system should be allowed.)
m
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
b) and/or by then the FileZilla client already finished the login to the server and commands may need to be sent prior to logging in.
 
b) and/or by then the FileZilla client already finished the login to the server and commands may need to be sent prior to logging in.
  
A good example of a platform where this applies, is the IBM i operating system that is very popular with banks and other businesses due to its very "compliant" architecture, and because of its scalability and legendary reliably and stability and Open Architecture.  Today's IBM i runs on the IBM POWER family of systems along with AIX(UNIX) and LINUX operating systems.  With many built in languages, including PHP natively running, the IBM i is positioned to continue to be a system of choice for companies that want a system that is reliable.
 
  
 
There is a workaround using the post-login command feature of the site-manager. Add a new site-manager entry and close FileZilla. Next open sitemanager.xml in the settings directory of FileZilla and add a PostLoginCommands element inside the Server element. Inside PostLoginCommand, use the Command element, with the actual command to execute as text.
 
There is a workaround using the post-login command feature of the site-manager. Add a new site-manager entry and close FileZilla. Next open sitemanager.xml in the settings directory of FileZilla and add a PostLoginCommands element inside the Server element. Inside PostLoginCommand, use the Command element, with the actual command to execute as text.

Latest revision as of 15:54, 23 October 2017

Some outdated servers default to legacy file systems not supported by modern FTP clients such as FileZilla. Modern FTP software implements TVFS as defined by RFC 3659 instead.

When the FTP server on such a legacy platform has its default set to use a filesystem unsupported by modern FTP clients, then you may require some custom commands to be issued to tell the FTP server to expect a more modern Unix/Linux or Windows file system syntax, so that the server can successfully communicate with modern clients. Manually entering these commands in FileZilla does not work as: a) they do not apply to the transfer connections which are separate from the browsing connection b) and/or by then the FileZilla client already finished the login to the server and commands may need to be sent prior to logging in.


There is a workaround using the post-login command feature of the site-manager. Add a new site-manager entry and close FileZilla. Next open sitemanager.xml in the settings directory of FileZilla and add a PostLoginCommands element inside the Server element. Inside PostLoginCommand, use the Command element, with the actual command to execute as text.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<FileZilla3>
    <Servers>
        <Server>
            <Host>127.0.0.1</Host>
            <Port>21</Port>
            <PostLoginCommands>
              <Command>PWD</Command>
              <Command>QUIT</Command>
            </PostLoginCommands>
        </Server>
    </Servers>
</FileZilla3>


If connecting using this site-manager entry, these commands get executed in the transfer connections as well.