inetdif it doesn't work (and we recommend running it standalone anyway). You can run it from a shell session.
Run W3C httpd from your terminal turned on, with a different port number like 8080:
httpd -p 8080Note: You must be
root(under VMS, have some privilege) to run with a port number below 1024. If you select a port above 1024, then you can run as a normal user. This way, anyone can publish files on the net. Howeever, it isn't very reliable, as your server will not automatically come back up if the machine is rebooted. In the long term it is best to install it to be started from the system startup file
You may not be able to use a port number which has been used by a
daemon process recently (port may still be bound), so you may have to
switch port number if you ^C and restart
httpd. When it
is running like this, you can also read the debugging messages (when
-v option), and use a debugger on it if
necessary. (See also: telnetting to the
-voption to turn on debugging messages. Use
-vas the very first command line option (this way debugging is turned on right away). You will see the daemon setting up the rules for translating requests into local URLs, and you will see its attept to access the file (assuming you map requests onto files).
httpd -v -p 8080Try to access the document from a client using another terminal window. Look at the debugging output. It will probably explain what is happening. If you still can't figure out the problem, mail your local guru help desk or if desperate
email@example.com a copy of debugging output.
httpdtry just running it with the terminal and typing
GET/document/url into its input:
httpd -v GET /document/url