30 Sep 2002
                Manager: A Remote File Manager for the SREhttp/2 web server.

MANAGER allows you to remotely manage files on your SREhttp/2 web server. 

                         -------------------------------
Contents.

I.   Introduction
II.  Configuring MANAGER
III. Starting and Using MANAGER
IV.  Multiple File Downloads

                         -------------------------------
I) Introduction

With MANAGER you can:
  a)  delete, copy, and move multiple files
  b)  extract and unzip .ZIP files
  c)  upload files
  d)  download many files at once
  e)  edit small files
  f)  remove directories
  g)  search for files in/under a directory

MANAGER has several security features, including control over what directories
are accessible, and a requirement that clients have a "dynamic password".

  a) Viewable directories.

     MANAGER will only access directories (and subdirectories of a directory)
     in explicitily listed directories.  There are a few shorthands,
     which allow you to "make accessible" the SRE2003 data directory (the
     root of your web tree), virtual directories (defined in the possibly
     host-specific ATTRIBS.CFG), the SREHTTP2 directory, and the SRE2003
     directory.
        See MANAGER.CFG (in your SREHTTP2\CFG directory) for the details.

  b) MANAGER uses SREhttp/2's "dynamic passwords" for more secure access 
     control.

SECURITY NOTE:

   MANAGER does NOT encrypt communications. Nor does it attempt to
   obsfucate what files & directories are being worked on.  Hence, if security
   is a major concern, MANAGER should be used cautiously -- for example, make
   sure that the MANAGER.CFG file is NOT in an accessible directory (see
   below for details on designating accessible directories).

   Note that, by default, MANAGER is disabled.

II) Setting up MANAGER

The MANAGER.CFG file, in your SREHTTP2\CFG directory, contains several
parameters. The most important is the ALLOWED_DIRS. parameters.
These MUST be set, or MANAGER will do nothing (by default, MANAGER
does not set any ALLOWED_DIRS).

You can edit MANAGER.CFG with your favorite text editor -- it is well
documented.

Note: MANAGER use cookies to implement dynamic passwords. 
      Thus, if you've disabled cookies, MANAGER will NOT work.
   

You also will need to set up a username entry (in your possibly host-specfic
USERS.CFG file) that has:
  1) A "MANAGER" privilege (or a SUPERUSER privilege)
  2) A ?MANAGER:apwd "secret privilege"

When you first start manager, you will be asked to provide your username
and password. Assuming that this username & password is legit, and has
a MANAGER privilege, you will then be asked for a dynamic password (the "apwd").
Note that everyone is required to provide a dynamic password, even SUPERUSERS.

                         -------------------------------

III) Starting and Using MANAGER

   After configuring MANAGER.CFG and setting up a username, just use your frames and 
   javascript enabled browser to send a /MANAGER? request to your server.

   For  example, if your server is foo.bar.net, enter the following in 
   NetScape 4.61's Location: line:

        http://foo.bar.net/manager?

   You will be presented with a list of the ALLOWED_DIRS. directories.
   Or, you can invoke the "frames" version of MANAGER.

   Assuming you opt for the frame version, 2 windows will be created.
   The main-window  contains two frames, the file-directory display area,
   and the control panel. The other window contains a directory tree.
   Note that if you "view" a file on the server a third "VIEWER" window
   will also be created.
   
   Once MANAGER loads it initial screens, it is largely self explanatory. 
   
Notes:
   * you can display listings using a "quick" (fewer options) or regular
     (more options, but takes more space) mode; and you can also display files 
     sorted by name or by extension.

   * uploads are to the currently selected directory

   * "editing" files is done via a <TEXTAREA> in a form. You can only edit
      text files, and by default they can't be larger then MAX_EDIT_SIZE bytes.
      You can override this on a file specific basis, but it can never be
      larger then  SRE2003's "LIMITBODY" parameter.

   *  A client can override the MAX_SIZE_EDIT, COL_SIZE_EDIT, and 
      ROW_SIZE_EDIT on a request  specific basis. To do this, the 
      client should enter three integers in the  "Destination" text box 
      (the box at the end of the row containing the file to be edited). 

      The first number should be the MAX_SIZE_EDIT (in kbytes), 
      the second  should be the COL_SIZE_EDIT (in columns),
      and the third should be the ROW_SIZE_EDIT (in rows).
      For example:
         60 100 25   -- 60kbyte maximum, use a 100 column x 25 rows 
                        TEXTAREA box
      Alternatively, you can use * as a MAX_SIZE_EDIT. The * means "use
      the "SRE2003 LIMITBODY parameter" (typically 500k). For example:
         *  80   -- Use the SRE2003 "LIMITBODY size limit", and an 80 col TEXTAREA


   *  see the next section for some important information on multiple downloads

   *  You can directly extract information from a ZIP file, extract (with/without
      overwrite) a file to the current "server" directory, or extract an
      entire ZIP file to the current server directory.  

                         -------------------------------

             
IV) Multiple File Downloads
   
    The "download" option allows you to download (from the server
    to your compter)  many files at a time.  

    There are 3 methods of downloading, which are good for different
    circumstances:

     1) Download as multipart/mixed -- binary
           This is the prefered method -- requires an up to date browser 
           (say NetScape 4.61). You will be asked for file names for
           each file you are downloading.

     2) Download as multipart/mixed -- mimetype
           If the files are "browser displayable" (i.e.; text/html or
           image/gif), then  multipart/mixed is essentially a
           is a server push of a series of documents & images.

           If you choose this, you can also set the delay time
           (in seconds) between "parts" (but don't set it to high, 
           you could time out the server!)   

     3) Download as application/x-sre-mixed
           This proprietary  method is meant to be used by older browsers that do not
           properly implement multipart/mixed -- binary.
           It is meant to be handled by the DoMixed.CMD "browser application" 
           (that is installed to your WWW\SRE2K\SREHTTP2 directory).

           To use DoMixed.CMD, you should be using NetScape on an
           OS/2 machine. The following setup should be done once:

             1) Open NetScape "applications". 
                    for NS4.04 -- look in Edit-Preferences-Applications
                    for NS2.02 -- look in Options-General_Preferences-Applications

             2) Create a "new type" with:

                   Mime Type: application/x-sre-mixed
                   Application to Use: cmd.exe /c "x:\dir\DoMixed.cmd"

                where x:\dir\ is the path you copied DoMixed.CMD to.
                Note: the "s MUST be included in thisr definition!
           
            When using this option, you may be asked to "load" or "save" the 
            file -- choose "load".  DoMixed will then run, and will ask
            you where each file should be copied to.
            
            DoMixed.CMD contains one user-changeable parameter: 
                DEFAULT_OUTDIR : The default directory to write files to.
            You can changes this at any time -- be sure to use a fully
            qualified directory name!

            If you are using a non-OS/2 client, you still might be able
            to use DoMixed.CMD -- it's a REXX program, and it should
            be possible to instruct your browser to run a REXX
            emulator.

          Note: If you expect people to use this mode, be sure to inform your clients 
                as to where they can find DoMixed.CMD. As noted above, a copy of
                DoMixed.CMD is installed to the SRE2K\SREHTTP2\DEMOS directory
                (under your WWW "data-directory").

.end of documentation                    
