Dhttpd just serve static pages. The only add-ons are an optional directory listing feature, and the ability to lookup hosts for logging purposes. For production website, something like thttpd would be a better bet.
Doesn't run external programs (no cgi-bin support), so this webserver cannot be easily hacked:
* Does not need a permanent IP Address. * Memory efficient. * Low profile. * Quick. * Just transfers files. * Can be run from a user account on high ports. * No configuration necessary. It just works.
|
|
|
| Architecture | Package Size | Installed Size | Files |
|---|---|---|---|
| alpha | 27.5 kB | 136 kB | [list of files] |
| amd64 (unofficial port) | 26.8 kB | 136 kB | [list of files] |
| arm | 25.9 kB | 128 kB | [list of files] |
| hppa | 27.3 kB | 132 kB | [list of files] |
| i386 | 26.5 kB | 72 kB | [list of files] |
| ia64 | 29.4 kB | 144 kB | [list of files] |
| m68k | 25.8 kB | 128 kB | [list of files] |
| mips | 28.2 kB | 144 kB | [list of files] |
| mipsel | 28.1 kB | 144 kB | [list of files] |
| powerpc | 26.6 kB | 128 kB | [list of files] |
| s390 | 27.0 kB | 132 kB | [list of files] |
| sparc | 26.2 kB | 128 kB | [list of files] |