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

fileUrl doesn't return a torrent or magnet link #78

Open
sucrecacao opened this issue Jan 22, 2022 · 2 comments
Open

fileUrl doesn't return a torrent or magnet link #78

sucrecacao opened this issue Jan 22, 2022 · 2 comments
Labels
upstream Requires updates upstream

Comments

@sucrecacao
Copy link

sucrecacao commented Jan 22, 2022

Hi all,

From the qbittorrent API , the fileUrl attribute from the search result should return a torrent or magnet link.

( running for example: `qbt_client.search.results(12345)['results'][0]['fileUrl'])

After a few tries, the values I got from fileUrl was always the same as the descrLink attribute.

Is this normal behavior?

@rmartin16
Copy link
Owner

Hello @sucrecacao,
I have not used the search functionality much myself; however, the qBittorrent team appears to have deferred the actual searching to teams with more familiarity with each search engine. Searching specific search engines is implemented via python scripts and those scripts return the values that are returned from qbt_client.search.results. So, I think if the URLs are not what you're expecting, the most likely issue is with the python script returning the wrong value. The management of these scripts, though, appear quite unorganized.....so, Im not too sure where to look for these scripts on github or elsewhere.....hope this help, though...

@sucrecacao
Copy link
Author

Yes, depending on the search plugin ( i.e. torrent source website ) I get a magnet link or the URL of the torrent webpage.

In case of the former, I'll just beautiful soup and try to find the magnet link in the webpage URL.

Would have been more clean to get a magnet link every time from the API, but my hacky solution should not be hard to implement. I just need to write a parser for every plugin I use.

@rmartin16 rmartin16 added the upstream Requires updates upstream label Jan 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Requires updates upstream
Projects
None yet
Development

No branches or pull requests

2 participants