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

First magnet link "in session"? gives 404 error #17

Open
abs0 opened this issue May 7, 2018 · 4 comments
Open

First magnet link "in session"? gives 404 error #17

abs0 opened this issue May 7, 2018 · 4 comments

Comments

@abs0
Copy link

abs0 commented May 7, 2018

The first magnet link I open gives a 404 error showing a URL of the form:
http://www.transmitter.web-extension/magnet%3A%3Fxt%3Durn%3Abtih%3A7KW5HVDIXUWV5XTOMIJLN6S4EAHQ5PJL

Its not immediately clear what a "session" might be here - restarting the browser does not trigger. Could be affected by cached DNS lookup?

@valpackett
Copy link
Owner

hm, weird.

If it doesn't happen when restarting the browser, how else did you restart the "session"?
Does refreshing the 404 page do anything?

@abs0
Copy link
Author

abs0 commented Nov 19, 2018

Whatever odd "session" behaviour has now gone away. Clicking on a magnet link now always fails with a 404 error showing a URL of the form
http://transmitter.web-extension/magnet%3A%3Fxt%3Durn%3Abtih%3AJYJLRECEIZIC44VLXU2JVMF462NQSUNN

while right clicking on the link and selecting "Download with Transmission remote" always works.

Have tried disabling all other extensions. Firefox 63.0.3 on NetBSD/amd64

@et304383
Copy link

I see the same behaviour too. I dunno if you manage the Chrome Extension too but it doesn't do it there.

In Chrome, the download just starts in the background on transmission and doesn't attempt to open the Transmission Web UI.

Could you maybe stop trying to open the transmission web UI? I don't know why anyone would need this to happen on every magnet link click.

@valpackett
Copy link
Owner

Could you maybe stop trying to open the transmission web UI?

Handling a URL scheme in an extension requires me to do something with the request. Redirecting to the web UI was the easiest thing to do. I guess a page that closes itself could be done too..

But anyway the 404 error on an internal transmitter.web-extension URL happens before that URL redirects to the web UI?? probably..

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

3 participants