Continued support for http localhost
This warning shows up when experimenting with Ziggeo locally, albeit on a non 80 port.
> Accessing the camera and the microphone on insecure origins (HTTP) is deprecated, and future browser versions will stop to support insecure origins. We highly recommend upgrading to SSL (HTTPS). For more details contact us at email@example.com
Is it possible to keep supporting the localhost domain for HTTP? It really reduces the barrier to entry and allows to simply spin up a static server in the project folder to start experimenting.
I agree Gavin, it would be great to have it supported as long as possible.
Having that said, the notice is shown by our system simply to let you know of browser specific requirements.
For example, screen recording works nicely with Firefox without any plugins. However Firefox requires the screen recording to be done over HTTPS pages.
On the other hand, WebKit based browsers require standard recordings to be done on HTTPS pages, as well as the screen recording.
This is what this notice is about and it should allow you to use your localhost and work properly.
The idea was to let all of the developers know of these requirements by browser vendors so that they have time to add HTTPS on their website before they implement any powerful features.
For example geolocation and video recording are just some of the features that are impacted by this.
Here are the references that show you more on this subject:
Please sign in to leave a comment.