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

Chrome is very slow to download file when iframe is sandboxed without "allow-same-origin" #1251

Closed
norzak opened this issue Dec 25, 2017 · 3 comments

Comments

@norzak
Copy link

@norzak norzak commented Dec 25, 2017

What version of WebTorrent?
desktop client Version 0.18.0 (0.98.5)

What operating system and Node.js version?
Macos 10.11.6

What browser and version? (if using WebTorrent in the browser)
Chrome latest

What did you expect to happen?
All browsers get the seeded file in microseconds. File is seeded on desktop WebTorrent client.

What actually happened?
Chrome gets the seeded file(380K 4-5 seconds) very slowly however Firefox and Safari gets it in a snap.

All browsers have asm.js warning on the console and uses latest webtorrent.min.js if that matters for chrome.

@norzak

This comment has been minimized.

Copy link
Author

@norzak norzak commented Dec 26, 2017

It looks like sandboxed iframe without "allow-same-origin" slows down the Webtorrent on Chrome to crawl. Any ideas why?

@norzak norzak changed the title Chrome is very slow to get WebTorrent Desktop seeded file Chrome is very slow to download file when iframe is sandboxed without "allow-same-origin" Dec 26, 2017
@norzak

This comment has been minimized.

Copy link
Author

@norzak norzak commented Jan 2, 2018

It is probably a chrome related problem not related to webtorrent.

@norzak norzak closed this Jan 2, 2018
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Apr 19, 2018

My guess is that the torrent file you're using has an HTTP web seed and when you don't have allow-same-origin, then the content can't be fetched over HTTP and only WebRTC works. So you're only getting data from peers.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.