Recent changes to SRE-http

Would you like to see a more complete history of changes?

Note on SRE2002

The GoServe based lines of SRE-http products will not be developed any further. Instead, we will be porting SREhttp products (and writing new products) for SRE2002.

Ver 1.3h contains the following changes & additions:
  • An SRE-http event manager (allows external processes to control SRE-http)
  • Support for delta-encoding, and experimental support for rsync differencing.
  • On-the-fly GZIP content-encoding is now supported (in addition to on-the-fly GZIP transfer encoding)
  • Faster GZIP encoding (uses a rxgzlib.dll instead of GZIP.EXE)
  • Minor improvements to the installation program, improvements to the DoGET program, etc.
  • What would you like to see?

Features added to recent versions include :

  • Ver 1.3g :
  • selector specific limits on number of simultaneous requests
  • improved support for advanced http/1.1 features, including transparent content negotiation and cache-controls.
  • Support for hit-metering trees (RFC2227)
  • Significant upgrades to the realm definition method of specifying selector-specific attributes.
  • Ver 1.3f:
  • Several XSSI Apache-style server side include directives, including nested if-elseif-else conditional ssis.
  • Selector-specific attributes can now be specified via a realm definition file (this complements & replaces the use of SRE-http's .IN files).
  • Ver 1.3e:
  • Ver 1.3e supports content-encryption based on a "shared-secret". In addition to encryption of responses, SRE-http supports a javascript based method of encrypting elements in a FORM.
  • A dynamic/encrypted password procedure, providing "digest-like" authentication to http/1.0 clients
  • You can now specify host & port specific parameter files.
  • sreLite: A smaller-quicker-less_feature_rich version of sre-http is now available.
  • A "pre-reply" procedure (a hook) can now be run just prior to returning content to the client (the content can be modified).
  • Wild card matching (of selectors to alias, access-control, and public_url entries) can now be limited to be "within a directory".
  • Return a list of "closest matching filenames" when a non-existent resource is requested (instead of the generic 404 response)
  • Y2K compliant