Many of the provider services are protocol adaptors, those being the
aecgi, fcgiprot, scgi, httpdand remote, whose purpose is merely to provide support for a
network protocol.
There are others in this category. These are the services that
provide direct functionality and really don't have any API to speak of.
The basicauthservice, while deprecated, provides the
ability to do basicauth (i.e. browser-based) authentication. It has
an API inasmuch setting of the
REMOTE_USERand
REMOTE_PASSWORDis an API.
The newer authservice provides the functionality that the
basicauthservice provides and more and is the replacement
now that basicauthis deprecated.
The rewriteservice allows for some pre-request URL
rewriting. In addition, named groups in the matched regular
expression will be added to CONNECTION.args if the
appropriate configuration variable is set. See the SkunkWeb
Operations Manual for details.
The userdirservice allows you to provide simple SkunkWeb
services to the users on your machine. If the URL starts with
~username, it will serve the pages from the directory
named by the userDirPath configuration variable
(public_html by default) in their home directory.
The extcgiservice allows SkunkWeb to directly handle CGI
programs. This is useful in the event that you either aren't running
Apache (or some other SkunkWeb compatible server), or that your
configuration is such that having your main HTTP server handle it is
either not aesthetically pleasing or just plain annoying.
The pycgiservice also allows SkunkWeb to directly handle
CGI programs, but pycgionly works for CGI programs that are
Python scripts. It handles them in such a way that, unlike
extcgi, does not require a call to fork, so should
provide better performance in the case that you are running a Python
CGI program.
