Summary of SRE-http 1.3h features

• Multiple hosts (either unique IP addresses, or multiple aliases per IP address) are supported.
  Seperate data directories, aliases, etc. can be specified for each supported host
• Logon requirements may be required of no one, everyone, or the general public.
  • A set of public resources can be specifed, which will be available to all clients.
  • OWNERS (with SUPERUSER privileges) and IN-HOUSE users can be automatically detected (using their numeric IP address), with logon requirements waived.
  • A set of "unallowed" numeric IP addresses can be specified.
  • Wildcards can be used in the list of IN-HOUSE and "unallowed" numeric IP addresses
• Several tools for resolving and redirecting requests are provided
  • A "directory specific" document can be sent when a request selector specifying a directory, but no file is name, is recieved
  • Instead of a default document; a "directory listing" can be produced, with file descriptions generated for all plain, html, and .ZIP files. These directory listings can be cached, and used for subsequent requests.
  • ALIASes can be used to redirect requests for moved documents, to resolve commonly occuring "misspelled requests", and to transfer specific files from anywhere on your server.
  • Server-side and client-side content negotiation is supported.
  • A customized "not found" document (complete with suggested link) can be sent when the requested document is missing.
  • The ~ shorthand for the "home directory" is supported. In addition, ~ can point to www-specific subdirectories of the "home directory"
  • Transfer of files from outside the "default data directory" is easily supported through the use of "virtual directories".
  • Transfer, with optional processing, of files from remote servers (without using redirection) is supported through the use of "remote" virtual directories.
  • * wild card character(s) in selectors can be used to request a "best matching" document.
• A variety of server-side includes are easily achieved
  • Global replacment-rules, that are not dependent on HTML-like statements, can be specified on either a general or file-specific basis.
  • A special caching algorithim selectively caches documents that contain server side includes
  • Headers and Footers can be included in all HTML documents
  • Recursively processed keyphrases, that dictate server side includes, can be placed in your HTML documents
    • Dynamic and Static String REPLACEments
    • Inclusion of files (from anywhere on your system)
    • Inclusion of OPTIONs that appear in the request selector (information after a ?)
    • Execution of REXX-code blocks, and insertion of the results
    • SELECTive excludes of HTML code blocks
  • The NSCA HTTPD server side include syntax is fully implemented
  • Easy-to-use support for client-specific and browser-specific customization of HTML documents
• Standard server features include:
  NCSA style IMAGEMAPS are supported, and easily requested.
  Searchable indices on text files are easy to setup
  A flexible mechanism for controlling access to explicit selectors (and the files they correspond to); including assignation of realms on a URI specific basis.
  Support for the HTACCESS method of access control
  Several mechanisms for recording hits
  Several forms of redirection can be specified
  A simple form of load balancing is supported
  Support for "common-log" format audit files (as well as browser and referer log files)
• Special SRE-http built-in features include:
  A file display and transfer facility with easy directory traversal
  A simple but powerful "text file" search facility
  Dynamic assignation of "short-term" privileges to clients
  Tracking of recent hits to prevent recording of repetitive requests
  Optional limits on frequency of unsuccesful "logon" attempts, with options for custom response files in the event of "logon" or "access" denial.
  Implementation of "byte range retrieval"'; using http/1.1 style Range: headers, or using modifiers to the URL
  Reponse headers can be automatially generated, using LINK and META HTTP-EQUIV elements in the <HEAD> portion of the document.
  A Content-MD5 digest can be added to all, or to a select set, of responses
  On-the-fly GZIP transfer-encoding is supported (both sending and recieving). GZIP and COMPRESS are also understood as content-encodings.
• Several file upload methods are supported
  Client directed retrieval of files from other HTTP servers
  Browsers that support the type=file FORM attribute (such as NetScape 2.01), can upload files from their own machines.
  The PUT verb, with byte ranges, can be permitted on a per selector (or per "set of selectors") basis
  The DELETE method can be permitted on a per selector (or per "set of selectors") basis
• User written server side processing (gateway programs) options include:
  Support for SRE-http addons (REXX routines that return results directly to the client).
  CGI-BIN scripts (both REXX and binary executables, and PERL scripts if you have a PERL interpreter installed) are supported (using procedures adapted from the GoHTTP package).
• A "pre-filter" can be called prior to invoking SRE-http
  SRE-http comes with a special pre-filter that implements the the GoRemote package.
• A "pre-reply" hook allows you to modify content (such as do a code page translation) just prior to transferring content
• A "post-filter" can be called after SRE-http has responded to the request.
  SRE-http comes with a special post-filter that uses socket calls, to an SMTP server, to e-mail "event specific" alerts.