After pondering some time about HTML GUI, I decided to go for that: Add two command line options -cfg_uri <uri> -protect <uri=path,...>
These options are not set by default. If -cfg_uri option is set, then SHTTPD gona show the configuration page if one goes to specified URI. -protect option can be used to password-protect this URI. (Also to protect any other URI, really, which overrides standard .htpasswd file protection for that URI). Also I changed the semantics of loading config file: o If config file is not specified as last argument after all options, shttpd tries to load "shttpd.conf" from current directory o If there is no shttpd.conf, it proceeds with defaults. o If config file is specified explicitely, shttpd fails if it cannot open config file. This allows to skip config file setting in the command line, and still load it. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ shttpd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shttpd-general
