SSL and external js file

I have an SSL enabled page that loads an external javascript file,
but the .js is giving an SSL warning dialog for an invalid certificate.  
What can I do about that?
LVL 2
kaller2Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

af500Commented:
Bring the external page internal :) I had the EXACT same problem. I do not think there is a way around this.
kaller2Author Commented:
It doesnt happen with our development server though.
af500Commented:
Does your dev server use a SSL cert? What kind of SSL cert do you have? Is it using a wildcard? I would love to find a solution to this as I have the *same* problem.

I have a self-signed cert on my dev box, and a real Thawte cert on my prod box.  I get a popup on both servers when the external JS is included, if I remove it everything works fine.

As far as I know, once you have code in your site that did not originate from the domain listed on your cert ... that will cause the popup because your code is not 'really yours' anymore as far as the browser / cert is concerned.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
kaller2Author Commented:
I may be dealing with some kind of local conflict with the hostname or proxy or caching problem, my hosting company report my site and certificate is working fine, and yes it is a signed certyificate with external javascript loading OK.

What fooled me was that when I accessed the production server from my development LAN, the js file triggered a warning.  But when I looked properly at the site certificate details it was MY LOCAL server certificate! that was doing it.  

Well it still is, so now I am looking into that, but at least I am a bit happier.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Servers

From novice to tech pro — start learning today.