
Here are my plans for the next major release of the Hiawatha webserver. All are configuration related.
VirtualHost {
...
UseDirectory = mydir[, ...]
}
Directory {
DirectoryID = mydir
Path = /files
...
}
Please, let me know what you think of it.
That said - if you're indeed going to re-do the config file I suggest writing an automatic migration script to allow current users to easily update their current config files. That will save you a lot of support work and hassle.
Keep on the good work dear Hugo!
Thanks.
+1 from me!
Thanks!
Source: https://mobile.twitter.com/hiawatha_ws/status/662332308054286336
Some time ago you thought about moving the config to a database, but you didn't. I fully agree, polling a database causes load at the wrong place, where the server core needs be as small and minimal, as possible, to run as fast as possible.
I also like the way you added Gzip support, zip once only.
Thanks for Hiawatha!
I can understand what this user means.
The hackers are searching for security issues with google. I would protect some security-related links by IP-Filter, so denied user see an error page (not found), which google will not list in search results
This would be very nice security feature,
Think about this Hugo.
There are currently plugins for Apache [github.com] and Nginx [github.com].
Can you ensure that there is also a plugin for Hiawatha?
It would be great
If it's already available can you point me to the howto? I tried to search for it and only found: https://dotbalm.org/http-caching-in-hiawatha/
If not, I'm requesting it. Maybe not 10 if it's not possible.
Thanks for the great software! I'm really excited to use Hiawatha 10 stable.
I have DocRoot in D:\HTTP and virtual subdirectories pointing to drive E: and F:. On my router I have DocRoot in /HTTP and shared directories in /mnt/usb1/
Your proposed change will break a lot of things.