Actually serve data on 8080, not just a redirect.
(This is not ideal but plenty of people seem to be confused by the redirect and how it interacts with NAT)
This commit is contained in:
parent
802f1f9404
commit
c144507471
10
debian/lighttpd/89-dump1090-fa.conf
vendored
10
debian/lighttpd/89-dump1090-fa.conf
vendored
|
@ -12,12 +12,12 @@ url.redirect += (
|
||||||
"^/dump1090-fa$" => "/dump1090-fa/"
|
"^/dump1090-fa$" => "/dump1090-fa/"
|
||||||
)
|
)
|
||||||
|
|
||||||
# Listen on port 8080 and emit 301s pointing to port 80
|
# Listen on port 8080 and serve the map there, too.
|
||||||
# to support the old convention of the map being on 8080
|
|
||||||
$SERVER["socket"] == ":8080" {
|
$SERVER["socket"] == ":8080" {
|
||||||
$HTTP["host"] =~ "^(.*):8080" {
|
alias.url += (
|
||||||
url.redirect = ("^/(.*)" => "http://%1/dump1090-fa/$1")
|
"/data/" => "/run/dump1090-fa/",
|
||||||
}
|
"/" => "/usr/share/dump1090-fa/html/"
|
||||||
|
)
|
||||||
}
|
}
|
||||||
|
|
||||||
# Add CORS header
|
# Add CORS header
|
||||||
|
|
Loading…
Reference in a new issue