→ 🚀What's New? Join Us for the Fall Product Launch! Register Now !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
joegasper
Engaged Sweeper
I've not encountered this issue for a few versions, but it just happened again. I had LS open in IE8 and using a HTTPS. The session to my LS in my browser was probably a day old, and the IIS session I'm pretty sure was "shutdown" (app pool) as LS was slow to respond when I did the following as my first access (pretty sure at this point, it's as it should be - and I did not have to reauthenticate). I entered a user's username in the search bar. As the LS apps spun back up, when it returned a couple answers automatically (dropped down from the search input field), that is when I got the mixed content warning. After this point, I've not received the warning again. I'll try to reproduce again by letting the session "time out".
4 REPLIES 4
joegasper
Engaged Sweeper
Fix confirmed in the latest beta.
Thanks!
Hemoco
Lansweeper Alumni
Please try the latest beta.
joegasper
Engaged Sweeper
Pretty sure it's IE8. Somewhere in the code to display the auto-suggest response. Couple resources that point to href=javascript...

http://blog.httpwatch.com/2009/09/17/even-more-problems-with-the-ie-8-mixed-content-warning/

http://blogs.msdn.com/b/ieinternals/archive/2009/06/22/https-mixed-content-in-ie8.aspx

I tried Fiddler and it looks good (need to pay for httpwatch to handle https). Pretty sure it's a way IE8 treats hrefs like "javascript:" and "about:"
Hemoco
Lansweeper Alumni
I am able to reproduce this in IE 8.

Can't reproduce it in firefox or chrome.

Are you able to see which html is giving the problem?
Could be a bug in IE