#1898 assigned defect

deep check on a non-directory gives unhelpful "400 Bad Request" error — at Initial Version

Reported by: davidsarah Owned by:
Priority: normal Milestone: soon
Component: code-frontend-web Version: 1.9.2
Keywords: usability error tahoe-deep-check verify Cc:
Launchpad Bug:

Description

Split from #1758.

If tahoe deep-check is run on a non-directory, it gives:

ERROR: 400 Bad Request
POST to file: bad t=stream-deep-check

For consistency, it should instead just check that object (with output in the usual deep-check format). It is probably the web-API operation that should change rather than the CLI command.

Change History (0)

Note: See TracTickets for help on using tickets.