On the torrent details endpoint redirect to the canonical info-hash if other original info-hash is used

[josecelano]

Parent issue: #275

Endpoint: GET http://localhost:3001/v1/torrent/0c90fbf036e28370c1ec773401bc7620146b1d48

Change torrent details endpoint returning 302 when the user uses any of the original infohashes if it's not the canonical one.

Context

After merging this PR #269, the Index stores the canonical infohash and the original infohash.

The infohash of the uploaded torrent might change if it contains a non-standard field in the info dictionary.

Problem

If you request the torrent details endpoint GET /v1/torrent/CANONICAL_INFOHASH the API will respond with a 404 status code because it only works with the canonical infohash.

Solution

Return a 302 Found pointing to the same endpoint using the canonical infohash.

We will use a temporary redirect instead of a permanent one because, in the future, we could return different data for the torrent with the canonical infohash and for other torrents in the canonical infohash group (torrents sharing the same canonical infohash).

cc @da2ce7

[josecelano]

@da2ce7 do you think we should do the same for:

• GET /v1/torrent/download/CANONICAL_INFOHASH (download the torrent file)

I think we can only use the canonical one for:

• Deleting the torrent
• Update the torrent info

The upload case will be treated as a new issue.

I think I would only change this endpoint and download (GET endpoints).

[josecelano]

It seems Axum removed the 302 case from the Redirect struct. The original PR had also the 320 Found constructor.

We can use the 307 but I do not know why they removed it.