From: SMTP%"ramsey@cua.edu" 24-MAR-1994 16:03:08.59 To: EVERHART CC: Subj: Re: WWW server or WAIS anyone? X-Newsgroups: comp.os.vms From: ramsey@cua.edu (Betsy Ramsey) Subject: Re: WWW server or WAIS anyone? Message-ID: Lines: 137 Sender: news@news.cua.edu (Guest Account) Reply-To: ramsey@cua.edu (Betsy Ramsey) Organization: The Catholic University of America Date: Thu, 24 Mar 1994 16:33:22 GMT To: Info-VAX@CRVAX.SRI.COM X-Gateway-Source-Info: USENET I pulled this information down from the CERN WWW server the other day. CERN HTTPD Public domain full-featured hypertext server. Authors TBL, AL Status: Mosaic forms and clickable image support, executable server side scripts to synthesize documents on fly. Possibility to plug in index search utility. Full Access Authorization support. Ability to act as gateway for anything in the WWW library's repertoire, including WAIS. Plans: PUT and POST pretty soon. Platforms Unix, VMS, VM/CMS (VM/XA). Next Milestone: PUT and POST. More information: User guide , Bug list , Internals , Change history . Wider scope: W3 servers , Other WWW software Problems? See FAQ (Frequently Asked Questions). Features include * Can act as gateway for HTTP, FTP, Gopher, WAIS, News, etc if needed * Can perform caching when running as a gateway * server-side executable scripts. * Forms and clickable image support; see demo. * Index search interface as a CGI/1.0 script. * Provides access authorization * Automatically generates hypertext view of directory tree * Uses "README" files to document directory listings * Configurable file suffix <=> content type mapping * Handles multiple file formats, encodings and languages of same file, selects format apropriate for client capabilities * Document name to filename mapping for longer-lived document names AL 10 Nov 1993 If you follow the link to the VMS server, the following information is provided: The vanilla daemon sources for VMS are available from CERN in: ftp://info.cern.ch/pub/www/src as: ftp://info.cern.ch/pub/www/src/wwwdaemon214vms.tar.gz. I modified those sources to enable implementation under Inetd with MultiNet, UCX or Wollongong TCPIP packages. The modified files are compiled and linked with the vanilla WWWLib for VMS, also available at CERN as: ftp://info.cern.ch/pub/www/src/wwwlibrary214vms.tar.gz. At popular request, I repackaged the vanilla CERN WWWLib as a zip: http://sci.wfeb.edu/www/sources/wwwlibrary214vms.zip (so you don't need to figure out how to deal with a .tar.gz archive 8-). MODIFIED SOURCES The modified daemon sources are in the archive: http://sci.wfeb.edu/www/sources/wwwdaemon214vmsMods.zip or: ftp://info.cern.ch/pub/www/src/wwwdaemon214vmsMods.zip and assume that you have set up a device:[WWW] or device:[foo.WWW] directory for the breakout, in register with your breakout of the vanilla WWWLib sources. The originals of modified daemon sources are included with _ori appended to their names. I've also set up an htbin script for building "on the fly" directory displays on VMS, and you can use it to look at the individual files on our system. WHAT TO DO WITH THE BREAKOUTS The directory [.WWW.214VMS.DAEMON.VMS] has BUILD_'transport'.COM and 'transport'.OPT files for building the daemon executables, with linking to the WWWLib_'transport'.OLB you should have built from the vanilla WWWLib sources, using VAXC on VAXen. If you have MULTINET, try using the supplied WWWLib_MULTINET.OLB. If there's a version mismatch, build the WWWLib with MMS or the BUILD_MULTINET.COM supplied by CERN in the library's VMS subdirectory. If you have UCX or WIN_TCP, build it with MMS, or edit CERN's BUILD_MULTINET.COM appropriately and build the library with that. Neither the WWWLib modules nor the daemon (httpd) modules and MMS or command files are set up for builds with DECC/AXP on Alphas. They need modifications along the lines we did for use of the library with Lynx. If you do not have the Lynx source set, please get it from: ftp://ftp2.cc.ukans.edu/pub/lynx (v2.2) for use as a model on how to do the needed modifications, before you contact me for help building it with DECC/AXP on your Alpha. Once you have succeeded in building the executables, read the header of the httpd.conf rule file, create an HTTPD_Dir logical for the directory containing the exectuables and scripts, create a WWW_Root logical for the data path root, place a Welcome.html in the data path root, and create a WWW_Root:[SCRATCH] for temporary files associated with script handling, all as described in the header of httpd.conf. Then execute SUBMIT_HTTP8001.COM to test the server as a detached process on port 8001. Your Welcome.html file will indicate whether the server's file and HTML handling work. I have included simple scripts, LocalTime.com to test its script handling, and WFEBGopher.com to test its "Location:" function (read their headers for a description of what they're supposed to do). If that all works, look over the Inetd configuration file I included, Inetd80.conf, edit my SpawnInit.com file appropriately for your own site, and then install the server under Inetd (a.k.a., MULTINET_SERVER or AUX) on port 80. If you're using a single Inetd server, you should be all set at this point. If you want to have a multiple server environment, e.g., the serious one on port 80 and an experimental one on port 8000, create an Inetd8000.conf for that, install it on port 8000, and define the system logicals HTTPD_CONFIG#, where '#' is each server's port number. I have added code to enable the master Inetd processor to track down the appropriate Inetd#.conf files for each server via the HTTPD_CONFIG# logical pointers to the configuration files. OK, if you've gotten this far and have the server built and checked out, it's time to start exploring the CERN server documentation for detailed explanations of how to use it. Fote ====================================================================== Foteos Macrides Worcester Foundation for Experimental Biology MACRIDES@SCI.WFEB.EDU 222 Maple Avenue, Shrewsbury, MA 01545 ====================================================================== I transferred these files down from sci.wfeb.edu yesterday, and successfully built a VMS UCX http server following the directions above. ------- Betsy Ramsey, The Catholic University of America, Washington, DC, USA Internet: ramsey@cua.edu Bitnet: ramsey@cua