🚀 go-pugleaf

Mike Meyer (mwm@contessa.phone.net) wrote:

[...]
: Alternative solution: run httpd standalone. I don't recommend that; as
: I don't trust the "multithreading" code. It works, but it's a black
: magic adaption of the Unix sources.

I also wouldn't recommend that -- there are some bugs in this mode:

- It keeps a lock on the last transmitted file. So, if you edit your 
  HTML-Files, save them, check them with your browser, edit again, 
  try to save -- not possible, you have to select another file with 
  your browser first...

- It can't handle two requests at the same time.

- After running for some time (several days) it can happen that it 
  does not answer any requests anymore. But you can "break" and 
  restart it then this happens.

- If it can't answer a request (because the file is not available -- 
  yet :-)), it quits. I made a little ARexx-Script that restarted
  it every time it stopped... :-)

After all I also put it in "Inetd"-Mode. But now, I use aws... ;-)

: Finally, I would *seriously* recommend that you not run httpd at all.
: It's got a major security hole in it, such that knowing users can run
: arbitrary commands (like "delete sys:#? all quiet") over the net.

Ups... I'm happy that know one didn't try it on my server... :-(
Upto now, I never worked with CGI-BINs, so I don't know which Bugs may
reveal itself in this area...


tschuess...
           Horst.

--
Horst H.G. Weber,    \\	 weberh@informatik.tu-muenchen.de
Augsburg, Germany     \\  webbasan@snafu.augusta.de 
                       \\  webbasan@mubo.augusta.de