SRE-http: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
mNo edit summary
 
Line 3: Line 3:
To use the SRE-http web server, you will need GoServe (a free, IBM EWS, OS/2 Internet server).  
To use the SRE-http web server, you will need GoServe (a free, IBM EWS, OS/2 Internet server).  


===Features===
==Features==
SRE-http ver 1.3h is a conditionally compliant http/1.1 web server for OS/2. SRE-http supports the usual server functions, including:
SRE-http supports the usual server functions, including:
*CERN and NCSA image maps
*CERN and NCSA image maps
*URL redirection, and a simple form of load balancing
*URL redirection, and a simple form of load balancing
Line 41: Line 41:
*Author: [[Daniel Hellerstein]]
*Author: [[Daniel Hellerstein]]


[[Category:Server]]
[[Category:Web server]]

Latest revision as of 13:36, 20 October 2019

SRE-http is a highly configurable http/1.1 web server for OS/2. With advanced features such as remote configuration, virtual hosts, caching and SSI; SRE-http is powerful enough for technically proficient administrators, but simple enough to be maintained by non-technical users. In addition, the Rexx based GoServe API (as augmented by SRE-http's numerous extensions) offers significant development advantages when creating web based applications, and when otherwise crafting a customized and enhanced web site.

To use the SRE-http web server, you will need GoServe (a free, IBM EWS, OS/2 Internet server).

Features

SRE-http supports the usual server functions, including:

  • CERN and NCSA image maps
  • URL redirection, and a simple form of load balancing
  • default documents for directories
  • common-log, browser-log, and referrer-log auditing
  • access controls by HTACCESS-file, by request selector, and by realm (SSL is not currently supported)
  • CGI-BIN compatibility

In addition, SRE-http ver 1.3h incorporates a number of special features, including:

  • an event manager (allows external processes to control SRE-http),
  • supports several forms of delta-encoding,
  • GZIP content (and transfer) encoding.
  • support for hit-metering trees
  • content-encryption using a shared-secret
  • http/1.1 features include byte range retrieval, server-side and client-side content negotiation, and support for multiple (virtual) hosts
  • a remotely executable configuration, with plenty of on-line help
  • a variety of cached server side includes (and conditional includes) are supported
  • META elements in the <HEAD> can be used to respond to HEAD method requests
  • local and remote (http) virtual directories can be specified and accessed
  • a caching directory display facility (with auto-description capabilities) to handle open-ended requests
  • file upload using FORMS (as supported by Netscape 2.01) and the HTTP PUT method
  • caching of recent requests (to suppress false recording of "new hits")
  • dynamic assignation of "short-term" privileges to clients
  • support for GZIP encoding (both sending or receiving)
  • lots of documentation & samples (but can there ever be enough?)
  • a growing list of WWW-aware applications provide BBS, discussion group, and numerous other features.

Documentation

Links

License