<P><IMG SRC="images/file_143" WIDTH=34 HEIGHT=34 ALIGN=LEFT>Netplex recognises a type of file called a <I>Configuration file</I> which provides access to advanced functions that would otherwise require a CGI program or similar magic to implement. The files are simply plain text with a defined structure, filetyped to 'NetpxCfg' (&143).</P>
<P>Since Configuration files are used for most of the advanced functions of Netplex, they are documented here rather than repeatedly explaining the format.</P>
<P>At present, there are four variants of Configuration files, they are:</P>
<P>The purpose of each of these is explained in the appropriate section. However, all Configuration files share a common format :</P>
<P>
<OL>
<LI>Any number of, or no, comment lines prefixed with the '#' character,
<LI>An identifier line,
<LI>Purpose-specific data.
</OL>
</P>
<P>For example :</P>
<P><PRE>
# An example Configuration file
#
Example
this:that:the:other
</PRE></P>
<P>This has two comment lines, an identifier line containing 'Example' and a line of specific data, the use of which depends on what the file's function is.</P>
<P>Configuration files are treated as special entities by the server, they will never be passed to clients as long as they're correctly filetyped. This is especially important for Client Authentication where the security of the password files must always be maintained. You <B>must</B> correctly filetype Configuration files if you want them to remain private. Once filetyped correctly, then Netplex will not 'see' the Configuration files and they will be reported as being 'Not Found'.</P>
