Menu
OK, I understand what the messages means, but I'm really not sure what's causing it. I'm using Safari and the Web Inspector on Mac OS X, by the way.
I've got the following in my document head:
<script src="http://local.url/a/js/jquery.js" type="text/javascript"></script> <script src="http://local.url/a/js/jquery.inplace.js" type="text/javascript"></script> jquery.js is handled fine, but the other file causes the warning. It also seems that the javascript in this file never gets executed.
The file is being served via mod_deflate, so it is gzip encoded, but so is the other file.
Has anybody got any ideas what's causing this, or how to resolve it?
Cheers all, Gaz.
973
MIME types also can not be misleading. MIME types are the authoritative declaration of what something is. If it's not that, then there is nothing misleading, it's simply invalid. Framing this as "MIME spoofing" is about as sensible as calling a buffer overflow in some font renderer "machine code spoofing".
MIME types enable browsers to recognize the filetype of a file which has been sent via HTTP by the webserver. As a result the browser is able to choose a suitable displaying method. Common MIME types are for example text/html for html-files or image/jpeg for jpeg-files.
A MIME type (now properly called "media type", but also sometimes "content type") is a string sent along with a file indicating the type of the file (describing the content format, for example, a sound file might be labeled audio/ogg , or an image file image/png ).
An image with an empty "src" attribute generates this error under Windows-Chrome:
<img src=""> ... whereas ...
<img> ... does not.
I arrived here because my ajax resultset was returning "src" data which was empty yet the img was still being inserted into the page.
191
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
