(c) Copyright 1994, Richard M. Troth, all rights reserved
HTTPD EXEC
HTTPD is the CMS HTTP Web server. By default, it runs on port 80,
but this and other parameters can be changed in the file HTTPD CONFIG.
HTTPD uses TCPSHELL EXEC to do "the hard work" of TCP/IP socket
management. For each HTTP transaction, TCPSHELL invokes HTTPD REXX
(because HTTPD EXEC told it to) to handle your HTTP requests.
This package is completely independent from other VM HTTPD
implementations. It is written entirely in REXX with REXX/Sockets
and CMS Pipelines. (no C code anywhere)
It works like GOPHERD in that it has a root FILELIST. Actually,
it can (as can GOPHERD) use an SFS sub-dir as the "root" server dir.
(it can probably use an SFS top-level dir for the root, but I've
never tried) The root menu for HTTPD, unless changed in your
HTTPD CONFIG, is called WEBSHARE.
Everything is served out as plain text (HTML or other) unless
otherwise specified in HTTPD CONFIG. A default HTTPD CONFIG file
is supplied containing some reasonable filetype mappings.
If a user on the host system has created a WEBSHARE directory or
FILELIST, objects listed there can be referenced with a URL like
http://vmhost.yourdomain/~userid/object
(note the tilde "~" (tilde); that's significant)
Note that the filename INDEX HTML is sacred. If a file by that name
exists, its contents are sent instead of an automatic index of the
SFS directory or FILELIST. Users can have their own unique INDEX
HTML, and I recommend that you use an INDEX HTML file for the
server's "root menu" because it looks so much nicer than a bland
LISTFILE-ish automatic index.
BE CAREFUL about mixing INDEX HTML in the same directory or FILELIST
with other FILELISTs. You won't damage anything, but you might find
confusing results. INDEX HTML always overrides an automatic index,
whether that's from a FILELIST or a LISTFILE on a directory.
This can work to your advantage.
For more information, position the cursor on
one of the following items and then press ENTER: