W3C httpd FAQ

W3C httpd FAQ

If you have problems, first make sure you're using the newest version. You'll find that out by peeking into our software archives

When something goes wrong the first thing you should do is to run httpd in verbose mode (the -v flag) to see exactly what is the problem. If you usually run it from inet daemon start it now standalone to some other port (with -p port flag) with otherwise the same parameters as in /etc/inetd.conf.

My Scripts Get Served As Text Files...

...or are completely unaccessible.

It's important to understand that rules in the configuration file (Map, Pass, Exec, Fail, Protect, DefProt and Redirect) are translated from top to bottom, and the first matching Pass, Exec or Fail will terminate rule translation.

So, make sure that your Exec rule is before any general Mappings.

How do I...


There used to be one zombie when running W3C httpd standalone; If you still see zombies (more than two that don't go away in a few minutes) it is a bug.

Inet daemon complains about looping...

...and terminates WWW service. :-(

This is a hard-coded inetd limitation on at least SunOS-4.1.* and NeXT, which limits maximum allowed connections from a given host to 40 per minute. This can be exceeded by scripts doing Web-roaming, or documents having masses of small inlined images.

There is a fix for at least SunOS inetd (100178-08), and in Solaris this is fixed. You can also run httpd standalone (preferably with the -fork command line option).

Most importantly, you should stop running httpd from inetd and rather run it standalone. This is because running from inetd is inefficient.

httpd@w3.org, July 1995