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.

Sign up for GitHub

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

Jump to bottom

Document that https or localhost are required for encrypted content #867

Closed
joeyparrish opened this issue Jun 9, 2017 · 3 comments
Closed

Document that https or localhost are required for encrypted content #867

joeyparrish opened this issue Jun 9, 2017 · 3 comments
Assignees
@TheModMaker
Labels
status: archived Archived and locked; will not be updated type: docs Improvements or fixes to documentation
Milestone
v2.2.0

Comments

@joeyparrish
Copy link
Member

It has been discussed on github and in the mailing list before, but encrypted content in Chrome (and according to the EME spec) requires either https or localhost. This should be made clear in the DRM-related tutorials and in the FAQ.

This issue was raised during this quarter's CWIP class.
@joeyparrish joeyparrish added the type: docs Improvements or fixes to documentation label Jun 9, 2017
@joeyparrish joeyparrish added this to the v2.2.0 milestone Jun 9, 2017
@chrisfillmore
Copy link
Contributor

From time to time I have had to advise people to use --unsafely-treat-insecure-origin-as-secure, perhaps the docs could also link to this page:

https://sites.google.com/a/chromium.org/dev/Home/chromium-security/deprecating-powerful-features-on-insecure-origins

@joeyparrish
Copy link
Member Author

Great advice. Thanks!

@TheModMaker TheModMaker self-assigned this Jun 19, 2017
@joeyparrish joeyparrish mentioned this issue Jun 22, 2017
Closed
joeyparrish pushed a commit that referenced this issue Jul 17, 2017
@TheModMaker @joeyparrish
Update tutorials and add another FAQ entry.
05aad5e 
Closes #862
Closes #866
Closes #867

Change-Id: I8e97750ddc9851a9d893f0d9aadab234a1deb988
@joeyparrish
Copy link
Member Author

The changes to the docs have been cherry-picked and will be released in v2.1.5.

@shaka-project shaka-project locked and limited conversation to collaborators Mar 22, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@TheModMaker TheModMaker

Labels
status: archived Archived and locked; will not be updated type: docs Improvements or fixes to documentation
Projects
None yet
Milestone
v2.2.0
Development

No branches or pull requests
4 participants
@TheModMaker @joeyparrish @chrisfillmore @shaka-bot