Article Options
- Subscribe to RSS Feed
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
Formerly, if you published a player on a page served by HTTPS, some browsers would generate a security warning. We've modified the JavaScript publishing code and added a secureConnections configuration parameter, so that you can now publish a player on an HTTPS page and not generate this security warning. Read more about how to publish a player on an HTTPS page.
Note that this does not cause the Brightcove player to use HTTPS; instead, it simply prevents the viewer's browser from generating security warnings that might otherwise be triggered by the player's communications.
Comments
You must be a registered user to add a comment on this article. If you've already registered, please log in. If you haven't registered yet, please register and log in.


