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

Closed
opened 2013-12-07 02:09:03 +00:00 by joepie91 · 6 comments
joepie91 commented 2013-12-07 02:09:03 +00:00
Owner

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
code-frontend-web
normal
defect
1.10.0
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
Author
Owner

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

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
Author
Owner

#1415 is tangentially related.

#1415 is tangentially related.
joepie91 commented 2013-12-07 11:07:43 +00:00
Author
Owner

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.

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
Author
Owner

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.

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.
meejah commented 2016-08-23 16:19:14 +00:00
Author
Owner

This would be useful for integration-testing to answer the question "is this node ready to actually-work".

This would be useful for integration-testing to answer the question "is this node ready to actually-work".
exarkun commented 2020-12-09 14:46:48 +00:00
Author
Owner

(https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2476) added a JSON version of the welcome page.

(https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2476) added a JSON version of the welcome page.
tahoe-lafs added the
was already fixed
label 2020-12-09 14:46:48 +00:00
exarkun closed this issue 2020-12-09 14:46:48 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2133
No description provided.