Skip to content

A deleted request still accepts a torrent pick or an interactive search #470

Closed

Description

@kikootwo

POST /api/requests/[id]/select-torrent and POST /api/requests/[id]/interactive-search look up the request by id without deletedAt: null. A user can still pick a torrent for, or search on behalf of, their own request after it has been deleted, which can start a download for a request that no longer shows anywhere.

The ebook routes (select-ebook, interactive-search-ebook) get the same deletedAt: null filter in #463, so a deleted request answers 404 there.

Expected: a deleted request answers 404 on these two routes as well, for its owner and for admins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions