Member Avatar for saucy6969
saucy6969 0 Light Poster

Hi there
I have just inserted my festival poster image on my site (bottom lefthand side) and it shows up and opens to the full image using safari/chrome/firefox just fine. IE just gives me the Red "X". Is this a fault with IE or did I miss something?

Any assistance would be greatly appreciated!

  • 1 Contributor
  • 0 Replies
  • 109 Views

Dani AI

Generated

@sa ucy6969 — Internet Explorer's red "X" almost always means the browser failed to load or render the image resource. The correct approach is to narrow whether the problem is the page/markup, the server response, or an IE-specific feature (mixed content, lazy-load, unsupported format). Quick checks and fixes are below.

First, isolate the image resource. Paste the image URL into IE's address bar. If it does not open there, the problem is server/path related. Open IE Developer Tools (F12) and watch the Network tab while reloading the page to see the request status (200/404/403/500) and response headers. From a shell, a simple header check helps:

curl -I "IMAGE_URL"

Look for a 200 status and a correct Content-Type such as image/jpeg or image/png. If the server returns text/html, attachment headers, or a 4xx/5xx code, fix the server or URL. If hotlink protection is in place, test with a Referer header:

curl -I -e "http://example.com/" "IMAGE_URL"

Next, check the HTML and client-side code. Ensure the img tag has a real src (not only data-src for lazy-load), and that a base tag isn't rewriting relative paths. Rename files to remove spaces/special characters or URL-encode them (use hyphens/underscores instead). If the page is HTTPS and the image is HTTP, IE may block it depending on security settings — serve the image over HTTPS or use a protocol-matching URL.

If the network shows 200 and the Content-Type is correct yet IE still shows the red X, inspect server logs for requests from IE user agents (some server rules treat UA/referrer differently), and try replacing the src temporarily with a known-good local image to rule out format/encoding issues. Common fixes: correct MIME mapping on the server, fix file permissions/path case-sensitivity, provide a proper src fallback for lazy-loading, and serve assets over HTTPS when the page is secure.

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.