We had the same problem. It turned out that in the css file we had a link to a image that was not used/referenced. That would trigger the server to send 404 but in http form, I think...let me confirm and get back
/Flemming On Fri, Apr 9, 2010 at 5:44 PM, Khan <[email protected]> wrote: > Currently my team of developers are experiencing an issue with > Internet Explorere 7 and 8 with our GWT application. > This works fine with FireFox, Chrome, and IE6. > When accessed through SSL(HTTPS), browser throws a pop-up security > warning of mixed content (resources from both HTTP and HTTPS) even > though our app doesn't use any HTTP resource while accessing through > SSL. So, the warning is definitely not triggered by mixed content in > our app. After researching a bit and debugging it feels like something > in the compiled JavaScript is triggering this warning message. Does > anybody know of this issue or any suggestion on how to tackle this > issue? This would be great if anybody could shed some light on this > issue. > > Not sure if this belongs to this forum. My Apology if not. Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
