The URL is not the problem here. Again it's the server that sends the wrong content type (application/octet-stream) for Firefox to display the image properly. Looking at your search for springfieldkarateandfitness.com one can see that this is not a generic case for this server. Only some unpredictable URLs are affected, unlike the cases we had before (blogspot, blogs.yahoo.co.jp). So adding a regular expression in the script code is some sort of an overkill and just based on trial-and-error. A script could check for problematic HTTP header in advance, but this would bloat web traffic for each page load because this has to be done for every picture to be really sure. High costs for some rare cases. <p>The URL is not the problem here. Again it's the server that sends the wrong content type (application/octet-stream) for Firefox to display the image properly. Looking at your search for springfieldkarateandfitness.com one can see that this is not a generic case for this server. Only some unpredictable URLs are affected, unlike the cases we had before (blogspot, blogs.yahoo.co.jp). So adding a regular expression in the script code is some sort of an overkill and just based on trial-and-error. <br />A script could check for problematic HTTP header in advance, but this would bloat web traffic for each page load because this has to be done for every picture to be really sure. High costs for some rare cases.</p> 2009-07-25T13:44:18Z 5059 Script 150535 29435 2009-07-25T13:44:18Z Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 9022