Provided that the viewer works in configuration as outlined at the beginning of this section, published video delivery can happen both in HTTPS (secure) and HTTP (insecure) modes. In a default configuration, the video delivery protocol strictly follows the delivery protocol of the embedding web page. However, it is possible to force HTTPS video delivery without regard to the protocol used by embedding the web page using the VideoPlayer.ssl configuration attribute. (Note that video preview in Author mode is always delivered securely over HTTPS.)
Depending on the method of publishing Dynamic Media video that you use in AEM, the
VideoPlayer.ssl configuration attribute is applied differently as demonstrated in the following:
If you publish a Dynamic Media video with a URL, you append
VideoPlayer.ssl to the URL. For example, to force secure video delivery, you append
&VideoPlayer.ssl=on to the end of the following viewer URL example:
See also (Linking URLs to your Web Application.
If you publish a Dynamic Media video with embed code, you add
VideoPlayer.ssl to the list of other viewer configuration parameters in the embed code snippet. For example, to force HTTPS video delivery, you append
&VideoPlayer.ssl=on as in the following example:
See also (Embedding the Video on a Web Page.