Old and Obsolete versions
For various reasons, not all experimenters are able or willing to update to the latest MIDAS version in a timely fashion. Therefore, documentation for old and/or obsolete versions of the MIDAS code and utilities will be moved to this area.
web server mhttpd
There was an important change to the web server mhttpd in MIDAS versions downloaded after May 2015. Prior to May 2015, mhttpd was insecure. The only way to secure this version was to run behind a firewall. As part of the May 2015 upgrade to MIDAS Security, a secure alternative to running behind a firewall was developed. The MIDAS Web Server mhttpd was explicitly linked with OpenSSL to provide secure HTTPS connections via the Mongoose web server. To connect to an experiment using mhttpd, a username and password are now required.
mhttpd - pre May 2015
- HTTP-only (pre-May2015) versions of mhttpd should only be used behind a firewall
- If Web Security is an issue, update to the latest version of mhttpd which uses HTTPS/OpenSSL.
-p port : port number e.g. 8080 (no default). See usage. [-h hostname ] : see Common Parameters to MIDAS Utilities [-e experiment] : see Common Parameters to MIDAS Utilities [-v] : display verbose HTTP communication [-D] : starts program as a daemon [-E] : only display ELog system [-H] : only display history plots [-a hostname] : only allow access for specific host(s). Several [-a Hostname] statements might be given [-help]
The command mhttpd -p port can be used to start the web server. In this case, the TCP/IP port number is required as an argument in order to listen to the web-based request.
e.g. if mhttpd is started on IP host machine "myhost" on port 8081 as follows
- mhttpd -p 8081 -D
access to the Midas status page can be obtained by pointing a web browser to
If multiple experiments run on the same host, a web server for each experiment must be started on a different port, e.g.
mhttpd -e expt1 -p 8081 -D mhttpd -e expt2 -p 8082 -D
Improve Security with SSL Proxy
Improved security for HTTP is gained by using an SSL (https) proxy. See Setting up an SSL proxy.