I maintain a recently secured intranet site (https//) that loads 2 external JavaScript files into. These 2 files come from an unsecured site which causes a frustrating warning message to display when loading every page. I have received many complaints about it the last few days
Hosting the 2 files on the secured site is not an option but are used with CSS and are required to view the page properly. If I load them with JS with <body onlaod=function> the page needs to be refreshed to view properly. Is there another way to dynamically load these 2 files to prevent the warning messages ?
Reply With Quote
Originally Posted by Nether
Bookmarks