Extra Site

There are further settings that will modify FXP.One's engine behavior which are not part of the definition of a site. Since we are allowed to define any variable name, which is automatically stored, some extra definitions have been created.

Since essentially Extra Site and Client Site commands are the same thing, they are separated because Extra Site lists additional commands which the FXP.One engine will act on. Where as Client Site commands are stored by clients, for clients. The FXP.One engine does not parse these key/value pairs.

• USE_XDUPE
• STARTDIR
• FXP_TLS
• IMPLICIT_TLS
• LISTARGS

Details

 USE_XDUPE=<yna>
 * Auto - If XDUPE is reported in the FEAT reply code, it will be enabled and used.
 * Yes  - Forced on, regardless of FEAT reply.
 * No   - Forced off, regardless of FEAT reply.

 STARTDIR=<str>
 * Optional extra for clients to issue CWD to <str> upon connection, instead of staying in default root "/".

 FXP_TLS=<yna>
 * Auto - Use secure (SSL) data transfers if possible, otherwise plain-text, using CCSN or SSCN.
 * Yes  - Always attempt secure (SSL) data transfers, fail if not possible.
 * No   - Do not attempt secure data transfers, always use plain-text.

The FXP_TLS option is added in addition to data_TLS as it was deemed insufficient for those who would like to force directory listings to use secure methods, but disable secure data transfers, even if sites supported such transfers. If FXP_TLS is not defined, FXP.One engine will use the default behavior as specified by data_TLS.

 IMPLICIT_TLS=<yna>
 * Auto - Do not use Implicit SSL/TLS 
 * No   - Do not use Implicit SSL/TLS
 * Yes  - Attempt implicit SSL challenge immediately upon connecting, before FTP commands.

LISTARGS

 LISTARGS=<str>
 * Usually, FXP.Ones uses default LIST arguments ("-lL") but you can over-ride that per site by setting LISTARGS.
 * For example, LISTARGS=-sl, or even "LISTARGS= " for no arguments.

Future

 MAX_SESSIONS=<int>
 * Limit number of sessions allowed for one site. Attempts to create another session will be presented with an error.

 MAX_QUEUES=<int>
 * Limit the number of active queues a site is allowed to be involved with. When GO commands are received
 * check the total active queues, and if already over the limit, leave queue in IDLE state. Automatically start queue
 * once an active queue goes to IDLE.