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

getUserMedia was supposed to work only via HTTPS, but web-dictaphone runs okay over HTTP on Android? #244

Open
mavavilj opened this issue Jan 2, 2024 · 6 comments

Comments

@mavavilj
Copy link

mavavilj commented Jan 2, 2024

Based on:

https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia

the getUserMedia() method should be available only in secure contexts (HTTPS).

However, I am deploying web-dictaphone on CivetWeb (https://github.com/civetweb/civetweb) locally and it seems to run fine over HTTP.

The browsers even say it's truly an insecure context.

@mavavilj
Copy link
Author

mavavilj commented Jan 2, 2024

And yes it does say that localhost is considered secure, however I thought it would still require HTTPS.

@mavavilj
Copy link
Author

mavavilj commented Jan 2, 2024

@mavavilj
Copy link
Author

mavavilj commented Jan 3, 2024

Or it means like it says on:

https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts

Locally-delivered resources such as those with http://127.0.0.1 URLs, http://localhost and http://*.localhost URLs (e.g. http://dev.whatever.localhost/), and file:// URLs are also considered to have been delivered securely.

But then it's confusing that Firefox still marks it as insecure.

@guest271314
Copy link
Contributor

But then it's confusing that Firefox still marks it as insecure.

Firefox doesn't mark HTTP as insecure.

@mavavilj
Copy link
Author

But then it's confusing that Firefox still marks it as insecure.

Firefox doesn't mark HTTP as insecure.

It does.

@guest271314
Copy link
Contributor

Where? I just created an HTTP server with node and successfully use getUserMedia() on http: protocol on Firefox Nightly 123. I didn't observe any notifications http: was "insecure".

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

2 participants