Member Avatar for Simon_4
Simon_4 0 Light Poster

I have the problem, that in the instector say me:

Resource interpreted as Image but transferred with MIME type text/html:

http://www.member-diving.com/

I have 3 video's on Youtube. All of them not works.

What could it be?

Kindly

  • 1 Contributor
  • 0 Replies
  • 220 Views

Dani AI

Generated

Quick diagnostic for : that Chrome inspector message ("Resource interpreted as Image but transferred with MIME type text/html") means an <img> request returned HTML instead of image bytes (commonly a 404 page, a redirect to the site homepage/login, or a script that outputs the wrong headers). prettyPhoto typically wraps a thumbnail image in an <a> that points to the YouTube URL; if the thumbnail URL returns HTML the lightbox won't open and the console shows that MIME-type warning.

Recommended checks (fast, in this order):

  1. Open DevTools → Network, filter by "Img", then reload. Find the entry whose Content-Type is text/html and note its Request URL.
  2. Paste that Request URL into a new tab to see what the server actually returns (homepage, 404, login page, etc.).
  3. Inspect the page markup to find the <img src="..."> that matches that URL. Confirm the src is a real image URL (not a YouTube watch page, site root, or a script that redirects).
  4. If the image is delivered by a script (image.php, proxy, CDN rule), ensure the script sends the correct header and no extra HTML or whitespace:
header('Content-Type: image/jpeg');
readfile($path);
exit;
  1. Confirm protocol consistency: use https links for YouTube/thumbnails on an HTTPS site to avoid mixed-content blocks.

Correct prettyPhoto pattern (example):

<a href="https://www.youtube.com/watch?v=VIDEO_ID" rel="prettyPhoto">
  <img src="https://i.ytimg.com/vi/VIDEO_ID/hqdefault.jpg" alt="thumb" />
</a>

<script>
$(document).ready(function(){
  $("a[rel^='prettyPhoto']").prettyPhoto();
});
</script>

Other possible causes to watch for: the video owner disabled embedding or the video is private (these prevent playback), server-side rewrites redirecting image requests, and Content-Security-Policy or X-Frame-Options blocking embeds. The Network tab and the exact console errors (mixed-content, refused to frame, or the MIME warning) will point to which of these is happening.

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.