Opened at 2013-01-03T01:28:03Z

Last modified at 2021-03-30T18:40:19Z

#1898 assigned defect

deep check on a non-directory gives unhelpful "400 Bad Request" error

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

Description (last modified by daira)

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 (6)

comment:1 Changed at 2013-01-03T01:35:54Z by davidsarah

  • Milestone changed from undecided to 1.11.0
  • Owner set to davidsarah
  • Status changed from new to assigned

This one looks a bit more complicated to fix than #1758, and I'd be happy to leave it to 1.11.

comment:2 Changed at 2013-09-01T16:43:12Z by daira

  • Description modified (diff)
  • Milestone changed from soon to 1.12.0

comment:3 Changed at 2016-03-22T05:02:25Z by warner

  • Milestone changed from 1.12.0 to 1.13.0

Milestone renamed

comment:4 Changed at 2016-06-28T18:17:14Z by warner

  • Milestone changed from 1.13.0 to 1.14.0

renaming milestone

comment:5 Changed at 2020-06-30T14:45:13Z by exarkun

  • Milestone changed from 1.14.0 to 1.15.0

Moving open issues out of closed milestones.

comment:6 Changed at 2021-03-30T18:40:19Z by meejah

  • Milestone changed from 1.15.0 to soon

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.