Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

OOTB Audio component in 6.2 - rendition in http so not working / Mixed Content

Avatar

Level 2

Hi,

I wondered if anybody can please advise me.

I'm using the standard audio component in 6.2.  In author it works fine, but when published and viewing on the site I get a 'mixed content' error and it doesn't work.

All of the other DAM assets work fine and point to https when we link to them from AEM and the sling mappings are working, it just appears to be audio component is auto linking to http.

On the page this is the error, in case this helps, which seems to indicate AEM is referencing a rendition in http ?

Mixed Content: The page at 'https://xxxxx.html' was loaded over HTTPS, but requested an insecure video 'http://xxxxx/content/dam/x/yyy/misc-/aaa.mp3/jcr:content/renditions/cq5dam.audio.aaa.mp3.html '. This content should also be served over HTTPS.

Thank you for your time,

Dave

1 Accepted Solution

Avatar

Correct answer by
Administrator

Are you talking about ACS Audio Component ?

I would request you to create an issue at Issues · Adobe-Consulting-Services/acs-aem-commons · GitHub

~kautuk



Kautuk Sahni

View solution in original post

2 Replies

Avatar

Correct answer by
Administrator

Are you talking about ACS Audio Component ?

I would request you to create an issue at Issues · Adobe-Consulting-Services/acs-aem-commons · GitHub

~kautuk



Kautuk Sahni

Avatar

Level 2

Hi Kautuk,

Thank you for the reply.  Sorry I thought the audio component came out of the box with 6.2, but in this case I will create an issue with Adobe Consulting Services.

Thank you.