no JSON output for node status (GET /?t=json) #2133

New Issue

tahoe-lafs · 2013-12-07T02:09:03Z

joepie91 commented

2013-12-07 02:09:03 +00:00

According to the Web-API manual entry for GET /, "By adding "?t=json" to the URL, the node will return a JSON-formatted dictionary of stats values". I cannot reproduce this intended behaviour on my machine, and get a standard HTML page instead:

I suspect this issue may have been introduced with the frontpage redesign.

According to the Web-API manual entry for `GET /`, "By adding "?t=json" to the URL, the node will return a JSON-formatted dictionary of stats values". I cannot reproduce this intended behaviour on my machine, and get a standard HTML page instead: ![](http://img.owely.com/screens/114413/original_owely20131207-18968-1y4lqx7.?1386382002) I suspect this issue may have been introduced with the frontpage redesign.

tahoe-lafs added the

labels 2013-12-07 02:09:03 +00:00

tahoe-lafs added this to the undecided milestone 2013-12-07 02:09:03 +00:00

daira commented

2013-12-07 04:19:08 +00:00

AFAIK there has never been a JSON version of the Welcome page.

tahoe-lafs modified the milestone from undecided to eventually

2013-12-07 04:21:23 +00:00

tahoe-lafs changed title from ~~JSON output for GET / broken~~ to no JSON output for node status (GET /?t=json)

2013-12-07 04:21:23 +00:00

daira commented

2013-12-07 04:22:37 +00:00

#1415 is tangentially related.

joepie91 commented

2013-12-07 11:07:43 +00:00

I feel that the ability to retrieve the Welcome page in JSON format (as documented) would be an important feature. In my particular usecase, I'm trying to implement storage grid monitoring/alerting - machine-readable connection status data would be essential for that. I'm reasonably sure that I'm not the only one with such a usecase.

daira commented

2013-12-07 15:03:31 +00:00

I agree it would be a useful feature. I think the next step is to write (fuller) documentation for webapi.rst, maybe with an example of the JSON that should be output.