[prev] [thread] [next] [lurker] [Date index for 2005/04/07]
Well, OK, film at 11 but listen to this particular piece of shit: We have a website, all shiny and new which we want to run under ssl. No problem, set that up, firefox happy, every darn browser happy except IE which complains about secure and insecure content on the same page. So we fix that hardcoded error (whoops :) but the error still remains. Nowhere in the html does it reference http://. So I dig out ethereal and there is definitely NO http call being made. What the fuck ? Much googling later, I get a clue here http://www.softcomplex.com/forum/viewthread_1868/page1/#pid5140 Yes indeedy people, in working around one IE bug, we tickle another ! For some reason <iframe src=""></iframe> is insecure. What crack were the programmers smoking the day they thought of that one ? So to get around it, I have to call a real html page from my webserver so that IE can believe it is secure. <iframe src="/brokenbrowser.html"></iframe> Useless, useless, fuckers. That's 3 hours wasted that I really don't have time to waste. Simon. -- "If you've never seen an elephant ski then you've never been on acid!"
Generated at 20:00 on 08 Apr 2005 by mariachi 0.52