When accessing Dump 1090 JSON from another web server, I found that the "Access-Control-Allow-Origin" parameter was set twice ("*, *") which Chrome objected to. By changing "add-response-header" to "set-response-header" we ensure that the correct header is sent, but never duplicated.
In recent versions of Firefox and (especially) Chrome, ".dev" domains are
force-redirected to a secure connection (HTTPS) instead of HTTP. Not
supporting an HTTPS connection makes for a bad user experience, so we want
to make enabling SSL support easy. Since we don't issue certificates, this
section is commented out by default, and it will require modification.
This is done primarily for PiAware, though it is applicable to just the
Dump1090 project.
Standard lighttpd will refuse to start if modules are loaded more than
once. Turn the module addition into a comment, explain why it's disabled
by default and in which cases you should enable it.
On some instances of lighttpd, like the one that comes with PiHole, the
alias module is not loaded by default. This makes the configuration of
PiAware's lighttpd not work (see e.g.
https://discourse.pi-hole.net/t/pi-hole-and-piaware-lighttpd/9611).
This way we ensure that the alias module is loaded even on non-default
lighttpd configurations.
/etc/default/dump1090-mutability is now generated in postinst,
if it doesn't exist, from a template in /usr/share/dump1090-mutability.
Subsequently, the config file is updated in place if debconf-driven
changes are made.
Static HTML/javascript have moved to a "html" subdir to avoid exposing
the template via the webserver.