OOTB Audio component in 6.2 - rendition in http so not working / Mixed Content | Community
Skip to main content
davenichols79
davenichols79
Level 2
October 19, 2017
Solved

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

  • October 19, 2017
  • 2 replies
  • 1879 views

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

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by kautuk_sahni

    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

    2 replies

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity ManagerAccepted solution
    Community Manager
    October 24, 2017

    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
      davenichols79
      davenichols79Author
      Level 2
      October 24, 2017

      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.

      Terms & ConditionsAccessibility statement

      Loading footer...