Member Avatar for brettsinn

Would a broken image inside of a "https" site cause the security prompt: "This page contains both secure and nonsecure items?"

  • 2 Contributors
  • 2 Replies
  • 62 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by brettsinn

Dani AI

Generated

Good follow-up, , and thanks to for the pointer. If you see the message "This page contains both secure and nonsecure items" it generally means the page attempted to load one or more resources over plain HTTP while the page itself was served over HTTPS. That kind of mixed-content request is what triggers the warning (MDN: Mixed content).

Quick troubleshooting: open Developer Tools (F12) and check the Console and Network panels for mixed-content warnings; run a project-wide search such as grep -R "http://" to find hard-coded insecure URLs; and inspect CSS (background images, @import), fonts, iframes, AJAX calls and any third-party widgets — those are common culprits. Also review server-side templates that generate absolute links.

How to fix: change asset references to HTTPS or use secure relative URLs, configure your server to redirect HTTP asset requests to HTTPS, or use a Content-Security-Policy with upgrade-insecure-requests as a temporary mitigation while you patch sources (MDN: upgrade-insecure-requests). Note browsers treat active and passive mixed content differently (scripts/iframes may be blocked; images may only warn). For behavior and recommended mitigations see the web.dev explainer (web.dev: What is mixed content?).

Recommended Answers

All 2 Replies

Member Avatar for jwenting

no, unless the image URI exists on another server (especially one that doesn't use SSL) from the one the html is coming from.
A broken image means no data is transmitted, so no potential security risk either.

At least that's the logical reasoning, you'd have to try it to see if it's what really happens :)

Member Avatar for brettsinn

no, unless the image URI exists on another server (especially one that doesn't use SSL) from the one the html is coming from.
A broken image means no data is transmitted, so no potential security risk either.

At least that's the logical reasoning, you'd have to try it to see if it's what really happens :)

Thanks for the answer, I actually found out what was causing it and you were right. It didn't have anything to do with the image.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.