http logging doesn't seem complete, even w/ -l debug

[mindsong]

http logging doesn't seem complete, even w/ -l debug

[troglobit]

It has been many years since I started patching up this fork, so I don't remember all the design decisions I made, but this project is not thttpd, so you cannot infer any behavior it had on this project. Also, the master branch is unreleased and still very much under development. The issues you mention about .deb package and out-of-sync command line options are not something I'll go into detail on, but I'd say normal state for an in-progress project. There's a lot of bigger issues to address before turning to fix them. Meanwhile, there are released versions (with lot less features) that I recommend to anyone who want to use this project for now.

[mindsong]

Hello Joachim (troglobit),

Thanks for the reply, and thanks for keeping this handy tool alive.

I appreciate that your make-over of the original thttp project is ongoing and quite substantial, if not almost a rewrite. I'm also very pleased that you have preserved the original "way of thinking" that Mr. Poskanzer designed into the original tool. Bravo for that.

I was hoping that the logging problem was a 'user error', or perhaps it was a runtime or compile-time setting that hasn't been fully detailed in the documentation yet. I can look into the repo and perhaps see if I've missed something. I expect that the logging code is present and mature, simply not enabled due to the way I am running the program.

I'm not at all worried that the deb package mechanism hasn't been updated. It only caught my eye when the file date in /usr/sbin was 2 years old and I had just built and installed it - that was unexpected, and made me wonder if I was doing what I believed I was doing. I'm glad to know that it's not unexpected at this point.

I have a great understanding of 'works in progress' that don't claim to be complete (current/master branches), but are treated as though they are complete anyway - look at the piles of projects on my desk for verification of that! :). My feedback is intended to help identify user-problems, or program issues before they become releases!

As mentioned before, thanks for your continued work this wonderful little tool. Perhaps I could help with some of the more peripheral updates to the codebase - e.g. documentation and examples of usage if that would be helpful. I will peruse the repo before I make promises that may be over my head!

best, and thanks for the reply,
--ms

[stappersg]

I also miss 200 OK in logging, same as in original report of this issue.