On Wed, Oct 22, 2014 at 02:28:11PM +0800, Paul Wise said unto me: > I'm missing some information in your question: > > How is the internal HTTP server used? dump1090 receives position reports from aircrafts via ADS-B and along with other options displays the locations of those aircraft on a Google Map based page served from the application. > Why did upstream feel the need to reimplement a HTTP server? I don't know for sure but the typical use-case is on a small embeded class system (Raspberry Pi being the most common), so I would guess that having the entire ecosystem in one binary was desirable for the original author. > What hostname/URLs does the internal HTTP server usually serve? Typically it just serves a static HTML page with some JavaScript that renders the Google Map and some data about the currently seen aircraft. It also constructs a JSON file to communicate with the JavaScript running in the browser. Upstream links most of the JavaScript (jQuery and associated libraries) from the Google CDN. As part of the packaging I have moved those to locally hosted files provided by various libjs-* packages. > Personally I would talk to upstream and get them to remove the > internal HTTP server. I am not sure they would be willing to completely remove the HTTP interface. I'm thinking about neutering the web server portion to only serve the internally-constructed JSON and moving the rest of the interface to a web server of the user's choosing. This would prevent any poor coding in the HTTP service from exposing any of the filesystem and would allow the front end web server to actually handle requests. --Matt -- Matthew Ernisse E-Mail: mernisse@ub3rgeek.net Web: http://www.ub3rgeek.net/ PGP Key ID: 0x4AE6BF32
Attachment:
signature.asc
Description: Digital signature