[tahoe-lafs-trac-stream] [tahoe-lafs] #1898: deep check on a non-directory gives unhelpful "400 Bad Request" error

[tahoe-lafs]

#1898: deep check on a non-directory gives unhelpful "400 Bad Request" error
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  davidsarah
  davidsarah             |     Status:  assigned
         Type:  defect   |  Milestone:  1.12.0
     Priority:  normal   |    Version:  1.9.2
    Component:  code-    |   Keywords:  usability error tahoe-deep-check
  frontend-web           |  verify
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by daira):

 * milestone:  soon => 1.12.0


Old 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.

New 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.

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1898#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage