If the purpose of the software is not to be a dedicated purpose http daemon, use something that already exists with a deep feature set that can be configured as needed for the purpose, such as apache2 with openssl or nginx.
It's not reasonable to expect that the developers of elastiflow reinvent the wheel and write their own httpd with TLS support, if it can be easily put "behind" apache2 or nginx. The risks of having people who aren't full time httpd specialists write their own http daemon and mitigate every possible security risk in a TLS setup are greater than using what already exists.
It's a one page size configuration file in nginx.