Can't add torrents from private trackers about chrome-deluge-remote HOT 9 OPEN

Not sure what's happening there TBH. Does this happen on all links or just some? I'm currently working on refactoring the code a huge amount, so hopefully this won't be a problem in the next release.

from chrome-deluge-remote.

hmm now that I check, it seems to only happen with my torrent site.. a general test from https://www.ubuntu.com/download/alternative-downloads works fine.

from chrome-deluge-remote.

Sounds like a bug I'd like to get fixed though... any way you could provide me a page that this is happening on?

from chrome-deluge-remote.

private site, i've sent you an invite. :)

from chrome-deluge-remote.

Aha. So the issue here is that the server requires your user session cookie, or else you get sent a 404. Since Deluge doesn't have your cookies, it gets a 404 and just sees it as a bad link.

I need to have the extension download the .torrent locally (so that your user session cookie is used) and send the raw data to deluge. This has been on my internal to-do list for a while.

from chrome-deluge-remote.

ahh cool. no rush, awesome you could figure out the reason though. Thanks!

from chrome-deluge-remote.

I'd love to see this implemented as well.

from chrome-deluge-remote.

Any updates on this? Having the same issue with a private tracker. Torrent files from regular sites seem to get added just fine.

from chrome-deluge-remote.

+1 for this feature, would be a great addition as it's my main use-case. (thanks for building this awesome chrome extension in your spare time!)

from chrome-deluge-remote.