![[<<]](pix/httpismall.gif){kind=small}
Back to the main page
launchd is now supported as an inetd-substitute
in 1.6.
OS X users who want to use Demonic should just roll a .plist like anything else for autostarting on bootup, with a tool like Launchd Editor (10.4+) or Lingon (10.5+).
stunnel is now supported as an inetd-substitute
in 1.6. This is the officially supported way to use HTTPi for SSL.
This support should be considered EXPERIMENTAL in 1.6, due to the
newness of this code and its high security requirements.
Do note that there is nothing precluding using stunnel for Demonic, but you will need to run Demonic HTTPi as a separate process and allow stunnel to proxy the port (transparent mode would be required for proper logging in this environment, however, which may not function on all OSes).
There are now several requests for this and it will be supported, but I am waiting for stabilization with Perl's IPv6 support before I do so.
Executables that die under HTTPerl in 1.4 and up and return control to the default handlers generate two log entries, one with a return code of 100 and another with the error code (usually 500). Although annoying, the code to defeat this on my inhouse test version turned out to be involved and unreliable, and for this reason I have left the double logging issue alone as a "feature to flag bad executables." It does not affect versions prior to 1.4.
Yes, I know this continues to be an issue. There seems to be some problem
with the Classic Mac MacPerl site, and it doesn't seem to have been updated
in some time. An ActiveState
port may become available, but I am (still!)
waiting for patches from one user who hacked
up inetd-based HTTPi to work in this environment.
There are success reports from Cygwin users, but I do not officially support Cygwin at this time (yet), and the reports did require some changes which I have incorporated partially in 1.6. Please let me know your results.