So why does the HikVision web cam interface continue to require this old, what Firefox calls, buggy, slow, and insecure, NPAPI interface? Clearly, they are a huge company with advanced technical products. * And finally, it can't be that HikVision is technically incapable. Also Chrome is clearly faster and even earlier booted this older interface. (Seems FireFox as of V52 abandoned this antique NetScape interface. * Next, this can't be for better performance, because the newer FireFox's native NPAPI interface that they require was built to be faster and more secure. No support for Firefox, Opera, Chrome, etc. * First, the reason can't be for better portability, because they now only work with the Edge browser, and thus only on Windows.
Let's investigate what that reason might be? There must be some good reason HikVision is STILL sticking with this old, Netscape era, NPAPI interface. I wouldn't expect this Firefox workaround to last forever unfortunately. However, a similar fix was present in the first version of Google Chrome that removed NPAPI plugins, and this was subsequently patched out. This only works when using TCP transmission protocol - NOT UDP. I have been unable to get this feature to work on the Firefox version of Mac OS X A context window should pop-upįor now, this should work as a temporary workaround to restore full functionality to your Hikvision system. Type about:config in the Firefox address bar – ignore the “are you sure you want to proceed?” page Chrome discontinued support back in September 2015, and you can see the impact this had in our thread on the topic.
This was announced in the Mozilla Future Releases blog post from October 8th 2015 and has now finally come into effect. This means that, much like Google Chrome, Hikvision users will no longer be able to successfully install the web browser plugin required to view their cameras in Firefox. Unfortunately, the time has finally arrived.Īs of Mozilla Firefox v52.0 released on March 7th, NPAPI plugins are no longer supported.
0 kommentar(er)
