See the changelog for details.

8 July 2020, 21:18
Successfully tested on OpenBSD, MacOS and Raspbian. Thank you.
Dale Farnsworth
9 July 2020, 01:25
Thank you Hugo. I upgraded my installation.
Chris Wadge
14 July 2020, 06:16
Took me a couple of days, since I was off the grid, but the deb repos are updated as well.
17 July 2020, 01:41
Thanks for the update I was waiting for these minor changes, this is very appreciated!
18 July 2020, 22:27
Awesome , very appreciated. I will try to convert it to rust with c2rust.
I'm very curious of the result, I'm sure it could benefit of few things like cargo and the ability to deploy from the .toml setup. it will also benefit from the ownership, borrowing , lifetime ( memory safety )
19 July 2020, 01:29
Thanks a lot for the new release!
28 July 2020, 14:23
Thanks Hugo.
25 September 2020, 13:48
I have used your web server for 6 years .Hope it will be a good different choice and host code on github . Someone will still need it Thanks Hugo.
Hugo Leisink
25 September 2020, 14:00
20 October 2020, 01:03
Hi Hugo!
Very good work, congratulations, Hiawatha is awesome!
Man, what about uWSGI for python?
Hugo Leisink
20 October 2020, 18:14
I have no plans for uWSGI support. You can take a look at this work around.
Chris Peachment
15 November 2020, 00:23
I'm still happy using Hiawatha after about 10 years. Just discovered a possible mis-use in the Toolkit -> Match -> Rewrite or Redirect statement. The original URL is still stored in the REQUEST_URI environment value for CGI while the new URL is correctly broken into new SCRIPT_NAME and QUERY_STRING values. Is it correct to have the REQUEST_URI unchanged after a rewrite/redirect? Problem arises when using golang http functions because they look at the REQUEST_URI first and only if it is empty do they look at SCRIPT_NAME and QUERY_STRING. If the values were consistent then it would not matter which is used. I don't know if other web servers keep the old URI after a rewrite/redirect but it does not look correct to me. Please advise. Thanks, Chris
Hugo Leisink
15 November 2020, 10:02
Hi Chris. Yes, it is correct to have REQUEST_URI unchanged. No matter what rewriting the webserver does, what was requested by the client stays the same. And REQUEST_URI should contain what was requested.
Chris Peachment
15 November 2020, 21:05
Thanks for the response. I solved the issue by forcing REQUEST_URI to be empty before the Go code attempted to use it. Thanks, Chris
8 January 2021, 05:52
I'm about to run two instances of hiawatha on one machine.

This triggers my brain, thinking about naming. Assume, we have one machine with several server processes running on it. These can be [0..n] instances of hiawatha, nginx, apache, postfix, ... .

The substring "www", which I find as sub-strings in the defaults for directory names, user names, ... sounds like a generalisation for all web-servers on one machine. But they are used as if there is one and only one web server. Same thing for "hiawatha". Shouldn't we have a more abstract distinction for the various names?

What should we put in such names
- purpose
- kind
- portnumber
- ...

Any inspirations, how I should name my stuff?