![]() This issue is being caused by Chrome changing its method of determining if a certificate is valid for a domain.Ĭhrome is now checking for a field in the certificate called "Subject Alternative Name". This field is not in the certificates that JMR generates in the HTTPS scanner and hence the failure reported by this new version of Chrome. Whilst we have fixed it here, it's now backlogged for release with the version 7 features which we are working hard on releasing within the next week.ġ. I enabled both the IE browser and the Google Chrome browser with the appropriate plug-in so that DISH Anywhere would play in a browser window. Use a different browser for AUTO captures that require the HTTPS scannerĢ. Turn off HTTPS scanning if you don't need to capture HTTPS content via Settings > Internet Downloads, Monitor HTTPS/SSL button It keeps saying that the DISH Anywhere App finds that the IE App Is not set to use Sling Player Plug-In. To disable Chrome auto update: On your Chrome browser's address bar, type in 'about:plugins' and hit ENTER. Find the plugin called 'Google Update' and click disable. Restart Chrome for the changes to take effect. You will receive an update notification via JMR when version 7 is available. As always this is a free upgrade.Last September we announced our plan to remove NPAPI support from Chrome, a change that will improve Chrome’s security, speed, and stability as well as reduce complexity in the code base. Since our last update, NPAPI usage has continued its decline. Today, the popular live TV streaming service Sling announced a new browser-based player for Google Chrome. Given this usage data, we will continue with our deprecation plan.Ĭurrently Chrome supports NPAPI plugins, but they are blocked by default unless the user chooses to allow them for specific sites (via the page action UI). The feature is in beta but it's available to all current Sling users. A small number of the most popular plugins are whitelisted and allowed by default. In January 2015 we will remove the whitelist, meaning all plugins will be blocked by default. ![]() In April 2015 NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store. Although plugin vendors are working hard to move to alternate technologies, a small number of users still rely on plugins that haven’t completed the transition yet. Our website provides a free download of SlingPlayer Web Plug-in 2.4. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI while they wait for mission-critical plugins to make the transition. The software lies within Internet & Network Tools, more precisely Browser plugins. ![]() ![]() In September 2015 we will remove the override and NPAPI support will be permanently removed from Chrome. Installed extensions that require NPAPI plugins will no longer be able to load those plugins.įor more details on the timeline, including guidance for NPAPI plugin developers, see the NPAPI deprecation guide. With each step in this transition, we get closer to a safer, more mobile-friendly web. ![]()
0 Comments
Leave a Reply. |