I believe this is expected behavior, even gmail does this if you have https turned on. What is keeping you from using https for loading the js? The browser doesn't know that the request you are sending doesn't contain any sensitive data, therefore this is a desired behavior as usually there is not real reason not to make a request once an SSL session has been established because at that point a symmetric block cipher is used which has very little overhead.
On Jul 14, 10:17 am, Danny Goovaerts <[email protected]> wrote: > I've deployed my GWT application over https. To allow caching of the > javascript files, I load the bootstrap script over http : > > <script language="javascript" src="http://www.cellamea.eu/cellamea/ > cellamea.nocache.js"></script> > > As expected, this gives a"mixed content warning" on Internet Explorer. > On Firefox and Safari, the site loads normally. > On Chrome (version 6.0.458.1 dev) however, I get a red "skull and > bones" icon in the URL address bar instead of the green padlock icon. > I think that this is even more scary for the users than the mixed > content warning on IE. > > Is this the expected behaviour on Chrome or do should I do something > different? > > Thanks in advance, > > Danny -- 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.
