Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

torrentqq: invalid download links #11389

Closed
ngosang opened this issue Mar 21, 2021 · 5 comments
Closed

torrentqq: invalid download links #11389

ngosang opened this issue Mar 21, 2021 · 5 comments

Comments

@ngosang
Copy link
Member

ngosang commented Mar 21, 2021

image

@garfield69
Copy link
Contributor

garfield69 commented Mar 21, 2021

This is a known issue. The config for this indexer has a warning about this site download links.

I know of no way to avoid the issue ATM.

Site's results page does not have magnets or .torrents or infohash
The details page has no magnets or infohash, but a single download href.

Essentially we look for a[href^="/torrent/download/"] on the details page, which matches for example, https://torrentqq79.com/torrent/download/304966, and this in turn it may delivers a 3rd party redirect, for example to https://www.filetender.com/kru3W2.
If the 3rd party does not return a .torrent, but instead presents a HTML page with a Invalid URL, Filename: file not found error message, or an HTML with a a countdown You can download the file in XX seconds. then Jackett's download breaks.

@ngosang
Copy link
Member Author

ngosang commented Mar 24, 2021

We can do a trick.

Details => https://torrentqq79.com/torrent/med/419131.html
Torrent (not working redirect) => https://torrentqq79.com/torrent/download/304966
Magnet => https://torrentqq79.com/torrent/magnet/304966

If you can replace the word download => magnet it should work for all torrents.

Btw, there is an infohash =>
image

@garfield69
Copy link
Contributor

does not work :-(
https://torrentqq79.com/torrent/magnet/304966 returns

<script>document.location.href="magnet:?xt=urn:btih:df26a0a25737eb4fdef27df651e9cc221835a51e";</script>

which the cardigann download processor is not expecting.

Also, while the infohash may be available on the details page, the cardigan processor's details-page-download block does not have that function.

@garfield69
Copy link
Contributor

note: d2906b4 is untested, as I get a flaresolverr timeout on the cloudflare check when I attempt to use the indexer.

@garfield69
Copy link
Contributor

v0.18.666

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants