https://bz.apache.org/bugzilla/show_bug.cgi?id=61662
--- Comment #5 from Kai <k...@gss.us> --- Eric, Precisely how is it 'silly'? Is there another command-line tool to query this information (aside from e.g. installing a browser) which is more suitable? Lucas, I don't know if there is a _strict_ need for this tool, but, then again, it's arguable we could do without most tools in most situations. The issue is that, without it, I'm not aware of any way without a web browser (or some facsimile thereof) to query that information; more particularly, the only way to access the information (as documented by the module) is through the web server on whatever host/port it's configured to listen on. What the tool offers is (in theory) a reliable, consistent, standard way to get this information. If it were designed properly, it would be useful for querying the status of a server quickly, without having to determine the listening port manually, install a web browser (even Links/Lynx aren't guaranteed to be present on a headless machine, and nonstandard ports may very well be firewalled, if apache is acting as a backend server for e.g. a nginx frontend), and type out the address and port in order to get the info one needs. I suppose curl makes a decent fallback for querying the status via ?auto, since that doesn't fill the screen with HTML markup, but then I'm just typing out the port manually every time instead of modifying the script every time I upgrade apache. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
