THIS SOFTWARE AND INFORMATION ARE PROVIDED "AS IS".
ALL USE IS AT YOUR OWN RISK, AND NO LIABILITY OR
RESPONSIBILITY IS ASSUMED. NO WARRANTIES ARE MADE.
hserv is a HTTP 1.0 compliant server with some features from HTTP 1.1 .
hserv is very configurable and funny and.
The main features are:
First of all run the installation script.
Let's suppose you installed hserv in PATH: (complete PATH: to a drawer).
Follow this basic installation:
Check if you have a services in inetd listening on 80/tcp or
hserv will fail with "can't bind socket" error.
hserv needs:
NOTA BENE:
wizard.library is not included in this archive but you can dowload it now.
I am Alfonso Ranieri .
My e-mail address is alfier@iol.t
You can find me on:
My home page is at http://users.iol.it/alfier
hserv is FreeWare.
You are free to detribute it as long as the original archive is kept intact.
Commercial use or its inclusion in other software package is prohibited
without prior consens from the Author.
Configuration options are read from a file, which is the first
argument of hserv .
If no file name is given, hserv tries to open /conf/hserv.conf
Each line of the configuration file is in the form:
<option> <value>
Empty lines, lines beginning with # or ;
lines after the 1024th, chars after the 256th
are ignored during parsing.
Words can be separated by space(s) and tab(s) .
The options are:
The Auth file consists of lines in the form:
<pattern> <realm> <login> <pass>
Due ARexx string-size limitation I set the max length of login":"pass to max 20 chars.
Anytime a file is requested, after it was parsed in a complete PATH: to a file,
and matches a pattern in a line of Auth file, an autentication request is send
to the client.
Try to join The Secret Garden
you'll need to login with l:secret p:garden
The RejectedIP file consists of lines in the form:
<pattern> <reasone>
If the pattern matches the ip, the connection is not accepted.
If a non empty Rejectedip file is given, HostNameLookups is set.
The Mimefile consists of lines in the form:
<mime> <ext> {SP ext}
Any file with an extension present in the left part of a mime line
is considered to be of that mime.
Default mime is <text/html>.
The Special file consists of lines in the form:
<pattern> <code> <file> [args]
An examples is
/#?/documentation.html CODE 301 Location: http://localhost/doc.html
that redirects documentation.html to the specified url .
The Handlers file consists of lines in the form:
<pattern> <handler>
If the pattern matches the file name, the file is considered to be of
one of the above type .
E.g. a line like
/CGI-BIN/counter REXX
will make hserv call the macro counter as it was a REXX macro rather
than an EXE macro .
hserv implementation of virtual host is really siimple and
not even so much tested.
The VirualHosts file consists of lines in the form:
<hostname> <DocumentDir>
On connection, the VirtualHosts file is opened and if the host
name of the request is found in a line, than the DocumentDir
specified is used; if the host name is not found, the default
DocumentDir is used. It also means, that for each virtual
host the default configuration is used, only the DocumentDir
can be changed.
To test virtual hosts, add in the host database of the stack you
are using, an entry like
127.0.0.1 www.alfie.org
Add in the VirtualHosts file a line like
www.alfie.org <path-to-somewhere>
and try to connect http://www.alfie.org with your browser.
The Errors file consists of lines in the form:
<httpCode/N> <macro> [newHttpCode]
If a http "httpCode" code is going to be returned by hserv,
e.g. the requeste document was not found and so hserv is
going to returns code 400, the Errors file is opened to
find a line with that code.
If the code is found, the macro specified is called as a
cgi (but the macro must be specified with complete path,
and doesn't have to be in the cgi-dir) and the output of
the macro is sent, with the originale code, if no newHttpCode
is specified, or with newHttpCode if present.
This is usefull to overwrite standard hserv answers.
hserv has a standard AmigaDOS template:
FILE,PORT/N
If the server runs as stand alone:
If the config file is modified, the server auto reloads it.
hserv (or better hs.rexx) does these controlls before sending a file:
The term CGI refers to:
The type of the macro is parsed from its file name extension:
You can overwrite the "type" of a macro, specifying a line in Handlers
A CGI macro of type perl will work if and only if you have perl
in your PATH , e.g. you have GeekGadgets installed.
A CGI macro of type REBOL will work if and only if you have rebol
in your PATH .
An exe macro can be an AmigaDOS script with the s bit set .
The directory CGIDir contains all the macro that are called in the form
"/cgi-bin/macro". It is a default directory for general porpouse macros.
CGI are called with the same arguments in the request.
They must write to stdout:
Macros have their real directory as CurrentDir.
If they are called from a <!CGI fun> the first 2 lines are discarded and the rest is inserted.
ONLY file with mime text/* are parsed.
Any time a file of mime <text/*> is encontered, the server makes this parsing on its' LINES:
The parsing is made for all but !CGI then for !CGI, but never recursively for !CGI.
hserv cames with a preferences editor GUI.
The GUI can be run via HservPrefs icon/macro.
It's template is FILE,PUBSCREEN/K,SERVER/K
The GUI is really easy to use, so there isn't so much to say.
At start it searches for:
If the gui is started by hserv itself via the ARexx command SHOW
an optional gadget "Close server" is present: it closes that istance
of hserv.
QuickStart is a little gui used to quickly run different istances of hserv.
