A project page can use a secure address while still referring to older media resources through insecure links. The resulting player may fail or behave inconsistently. Ask the website team to review the resource chain before assuming that the film's format is incompatible.
MDN's mixed-content guidance describes secure pages requesting resources through insecure protocols and the browser protections involved. The appropriate response is to correct the authorised delivery arrangement, not to tell visitors to disable those protections.
Look beyond the address bar
The page's own address does not show every resource it requests. A poster, caption file, player script or media address can retain an older reference after the website changes. Ask the implementer to inspect the actual requests and identify which resource is affected.
Keep the report concrete. State which page fails, what appears in the player and whether the problem affects the poster, controls, captions or picture. A precise symptom helps the technical owner separate mixed-content behaviour from other delivery problems that can look similar.
Avoid changing every address by assumption. A secure version of a resource needs to exist and be supported by its owner. The website team should confirm the correct current endpoint and any redirects rather than merely adding a letter to a URL and declaring the issue resolved.
Repair the source of the reference
Ask where the outdated link is stored. It may be in a page field, a reusable website component or a host integration setting. Correcting one visible page by hand can leave the same problem in other uses of the component.
If the reference comes from a supplied embed, ask the host owner for its current supported integration. If it comes from a migrated asset library, have the website team verify the new resource location. The production supplier can confirm which approved file is intended, but it may not control the website's stored addresses.
Test the resulting path through the actual audience page. A direct secure download is useful evidence, but it does not prove that the page has stopped requesting the old insecure resource. Ask the technical owner to verify the deployed request and then perform the ordinary viewing tasks.
A hypothetical old caption address
Suppose a builder's website has moved to a secure platform. Its project film plays, but a caption reference copied from an earlier setup no longer works as intended. Marketing sees the correct text file in its archive and cannot understand why the public experience is incomplete.
The website supplier identifies the outdated resource reference, confirms the authorised secure location and updates the component that supplies it. The reviewer enables captions through the live page and checks the expected content. No retranscription or film remake is needed to solve the delivery-reference problem.
Keep the correction safe and traceable
Record the old dependency, the approved replacement and the pages or components affected. Do not circulate sensitive resource URLs beyond the people who need them. If the required secure endpoint is unavailable, ask the responsible owner to choose a supported alternative rather than bypassing the browser's warning.
Discuss the approved project-film assets with Live Images. Confirm production scope, while website resource references, secure hosting and their verification remain with the authorised technical team.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.