Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a website on which we have recently enabled SSL. In most browsers, this works fine: our scripts and stylesheets are imported using HTTPS and most browsers load pages successfully. However, in some circumstances, secure pages will load without page styling or JavaScript.

One place we've reproduced this consistently is on Mac OS X (v10.6.4) with Safari 5. We have another user who reports consistent issues on Mac OS X with Chrome v5, but I see no issues with Chrome v6.

Safari reports to me that the certificate is not valid as it's signed by an 'unknown' authority (DigiCert). This complicates the situation since Safari in Windows doesn't have this issue. At least in Safari, however, a user can tell the browser to always trust content from the site and stylesheets and scripts will load appropriately.

Most Chrome users who encounter the issue have a similar error signature. However, one of them reports that his browser downloads the files with blank content. In these situations, Chrome's error console indicates the file was interpreted as the correct type but transferred with a blank MIME type.

The site itself runs Apache and the static content server uses Lighttpd.

The inconsistency of this issue is making it hard to pin down so any suggestions would be appreciated.

share|improve this question
    
Probably something regarding the root cert not being in the different browsers. I can see DigiCert's root cert not being widely distributed relative to larger CAs. –  Warner Jul 9 '10 at 23:13
    
I suppose that's possible although DigiCert claims to be compatible with the browsers in question: digicert.com/welcome/compatibility.htm –  Shaun Jul 10 '10 at 0:14

3 Answers 3

up vote 2 down vote accepted

This turned out to be a problem with how we set up the certificate on our static content server. It was set up in Lighttpd such that Safari could not follow the certification chain to the intermediary cert from the root cert. We had to stack the certs in a single file and move the server cert to a pem file. Afterward, Safari treated requests to our static server as valid and began serving the JavaScript and CSS to the browser again.

share|improve this answer

Did you put hardcoded references to the files with the full url? eg 'http://server/file.cs'

If the browser refuses to show insecure content for a secure web page then you will get the problem you describe.

share|improve this answer
    
The link and script tags in the head section of each page have a full URL simply because we serve the static content from a different sub-domain. However, the tags are constructed with the security level in mind; if you visit a secure page, it pulls the code via the HTTPS protocol rather than the HTTP protocol. –  Shaun Jul 13 '10 at 20:21

I had the same problem with nginx. According to DigiCert and the nginx docs, the site certificate and the intermediate certificate need to be concatenated:

http://www.digicert.com/ssl-certificate-installation-nginx.htm

http://wiki.nginx.org/HttpSslModule

cat intermediate_certificate.crt >> your_domain_name.crt

nginx (and in your case, lighttpd) don't have a separate SSLCertificateChainFile directive like Apache and instead need the certificates to be "chained" manually.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.