Clean up insecure asset references

An HTTPS page can still refer to images or scripts using HTTP. Browsers may upgrade or block these requests depending on the resource and context.

1. Identify the exact resource

Record the asset URL and the template or content that references it. A migration or old embedded code can be the source.

2. Check the secure version

Confirm the asset is available over HTTPS before changing the reference. Do not simply replace text across an unknown database without a backup.

3. Fix the source

Update the content, template or integration setting responsible. Clearing a cache alone will not repair a persistent source reference.

4. Retest the page

Check the browser’s network and console output and verify that the relevant image, script or stylesheet still loads.

When to ask for help

Stop if the change affects a critical workflow, requires access you do not have or produces a result you cannot explain. Keep the original evidence and a restorable backup. A short, well-defined repair request is easier to review than a series of speculative changes.

Related repair: request a scope review. Choose your platform on the request form; availability and price are confirmed before payment.