I don't get that error with IE7 on MY end. But who's to say. Firefox is show in 2 more recent posts than IE 7 right now. Maybe it doesn't read as quick either.
Juha
· 3 years ago
OK, this is going to be embarrassing, but... even though I checked the source on the page, I missed it.
I loaded an HTTPS version of Scobleizer, but that page had some elements served over HTTP. So, IE7 told me the page had "non-secure" items in it, and refused to serve'em up.
So, in summary:
1) IE7 was right to refuse to display all the page. 2) I'm a n00b for missing the obvious. 3) Scoble's a n00b too for mixing HTTP with HTTPS :). 4) Microsoft's IE7 team really, really, really should come up with error messages that tell you exactly what the hell's going on.
Fixed blog post on this subject coming up in a moment.
David Brunelle
· 3 years ago
I wrote a post on obtaining free software from Microsoft. IE7 thought it was a phishing site. Besides the comment fields asking for a name, email, and URL - I was in no way collecting personal information.
I determined the process of getting Microsoft to exempt my URL was not worth the trouble.
Juha
· 3 years ago
David: just checked with IE7beta3, and yep... you da phisher man. Well, your site is suspicious, says IE7. I wont hand over my personal information to you then. :)
False positives like these could have some interesting ramifications for Microsoft. Not the first one I've heard of either.
radaronpaws
· 3 years ago
Funny! But bitter! But funny! ;)
Abby
· 3 years ago
Maybe IE7 suspects your 'naked conversations' :D
shel israel
· 3 years ago
I am not that doo doo bird.
orcmid
· 3 years ago
In IE6 for me, It's the way the amazon.com ad for the book is handled. The Barnes & Noble image doesn't have the problem.
I get one warning per image on pages that have lots of amazon.com ads/referrer links, mostly because amazon.com is on my trusted site list and this blog isn't. I guess it is time to take them off of my trusted site list and see if their scripts all still work.
- Dennis
orcmid
· 3 years ago
Well, removing the trusted site designation from the non-HTTPS amazon.com URLs got rid of the unknown (mixed) designation. I don't see https fetches for the blog page, but posting a comment does generate some https action.
By the way, although I don't get a warning message now, I do get the little stop sign in the status bar, and my browser has blocked three cookies from amazon.com.
It annoys me when sites that I am not accessing directly put cookies on my system because they use fetched images to do it. (My blog does that to its visitors because I must show the blogger icon and Google happily drops cookies on all visitors who accept them.) So I can't write an honest privacy statement for my blog, which is on my own web site. Ick.
Molly C
· 3 years ago
David Brunelle, did you report your "phishing" problem to the IE team? After all, that's what betas are for, to get bug reports from scenarios in the field so the problems can be addressed.
All Comments
I loaded an HTTPS version of Scobleizer, but that page had some elements served over HTTP. So, IE7 told me the page had "non-secure" items in it, and refused to serve'em up.
So, in summary:
1) IE7 was right to refuse to display all the page.
2) I'm a n00b for missing the obvious.
3) Scoble's a n00b too for mixing HTTP with HTTPS :).
4) Microsoft's IE7 team really, really, really should come up with error messages that tell you exactly what the hell's going on.
Fixed blog post on this subject coming up in a moment.
I determined the process of getting Microsoft to exempt my URL was not worth the trouble.
False positives like these could have some interesting ramifications for Microsoft. Not the first one I've heard of either.
I get one warning per image on pages that have lots of amazon.com ads/referrer links, mostly because amazon.com is on my trusted site list and this blog isn't. I guess it is time to take them off of my trusted site list and see if their scripts all still work.
- Dennis
By the way, although I don't get a warning message now, I do get the little stop sign in the status bar, and my browser has blocked three cookies from amazon.com.
It annoys me when sites that I am not accessing directly put cookies on my system because they use fetched images to do it. (My blog does that to its visitors because I must show the blogger icon and Google happily drops cookies on all visitors who accept them.) So I can't write an honest privacy statement for my blog, which is on my own web site. Ick.