On 11/30/2016 07:20 PM, Jordan Gigov wrote: > I think a better approach than "?json=true" would be to to respect the > "Accept" header values of "application/json" and "text/json" if they > have the higher priority.
Or both? Practically speaking, showing JSON based on a query arg is vastly easier for laymen to implement in their applications than setting accept headers, AND you can query and get JSON in your browser also. > XML output should also be an option, if it will indeed serve as an API > end-point. Meh, I honestly have not used XML in a decade, so I'm +/-0 on that one. If someone wants to do it, fine, but .. :p > > On 30 November 2016 at 20:08, Luca Toscano <toscano.l...@gmail.com> wrote: >> >> >> 2016-11-30 19:03 GMT+01:00 Daniel Gruno <humbed...@apache.org>: >>> >>> On 11/30/2016 06:54 PM, Jim Jagielski wrote: >>>> I'm thinking about adding JSON support to mod_status... >>>> the "plain" version output really stinks and lacks parity >>>> w/ the info we provide via HTML, and it would be nice >>>> to produce a really easily parseable format. >>>> >>>> Thoughts...? >> >> >> +1, this will simplify a lot things like metrics collectors polling httpd >> regularly (that don't need a nice html format). >> >>> +1, a ?json=true or some such to the query would be helpful. >>> so you could do >>> /server-status?json=true >>> or >>> /server-status?auto&json=true >>> >> >> +1, I like the idea! >> >> Thanks! >> >> Luca >>