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

ZeroNet + Webtorrent = Chromium "Not allowed" error #783

Closed
webarthur opened this issue Apr 29, 2016 · 4 comments
Closed

ZeroNet + Webtorrent = Chromium "Not allowed" error #783

webarthur opened this issue Apr 29, 2016 · 4 comments

Comments

@webarthur
Copy link

@webarthur webarthur commented Apr 29, 2016

Blob links...

  • localhost/apache: blob:http%3A//localhost/0a375747-bfdd-422e-bb8c-7838cdec7c49
  • Webtorrent home: blob:https%3A//webtorrent.io/5368bdd6-53ca-4b03-a85b-fea682968cd6
  • ZeroNet on Firefox (works fine!): mediasource:null/c007f211-d859-4edc-b5f4-4a742e96e946
  • ZeroNet on Chromium (error) blob:null/84c9da13-bf32-4706-84ed-885b8c444b3d

Console output (on chromium):

Not allowed to load local resource: blob:null/84c9da13-bf32-4706-84ed-885b8c444b3d

Why? =/

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented May 4, 2016

Sorry -- I couldn't get ZeroNet to run on OS X. This is probably a ZeroNet issue. If you're able to figure it out, I'm happy to accept a PR.

@feross feross closed this May 4, 2016
@ndm13

This comment has been minimized.

Copy link

@ndm13 ndm13 commented Sep 8, 2016

Just came across this while doing local development. Apparently it's a long-standing Chromium bug that people run into every few months. I don't know a workaround, although one StackOverflow user worked around it by passing the data as an array (which obviously won't be feasible for WebTorrent.

@MuxZeroNet

This comment has been minimized.

Copy link

@MuxZeroNet MuxZeroNet commented Jan 30, 2017

Big thanks to the person who helped me re-report this Chromium bug. The new issue ticket is available at https://bugs.chromium.org/p/chromium/issues/detail?id=686516

Please star to make this issue more urgent and more appealing to Chrome devs.

@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 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
4 participants
You can’t perform that action at this time.