Den 22/12/2010 kl. 17.17 skrev Jakob H: > Hi, > > I have a Django site hosted on Bluehost, and I'm trying to get SSL to > work, but have some problems. I've got a dedicated IP with SSL > certificates all ready to go. > > 1. Whenever I enter a https://... I'm automatically re-directed to a > http:// address. I assumed that this cannot be Django related, and > only Apache related. Bluehost claims this is a Django related issue, > but I disagree. In general, what makes more sense? I also believe that > I do not have any Apache re-directs that directs https:// to http://. > Has anyone seen similar issues? I can provide more info if needed.
This is simple to test. Try serving a simple HTML page with Apache alone (bypass Django) and see if the redirection still occurs. The redirection can happen both places. > 2. I have a sub-domain to serve static files http://static.[domain].org. > I do this to avoid having static files served by Django through the > WSGI interface. As I understand, whenever I use SSL I must serve > static files via SSL as well. Will this cause problems if my SSL > certificate is only for my domain (www.[domain].org) and not for > static.[domain].org? What is the solution here? Do I either get two > certificates (one for 'www' and one for 'static'), or do I serve > static files via Apache in some other fashion (in that case, how?)? It is not mandatory to serve all parts of the page over SSL, but most browsers will produce warnings if you don't. What you need is either a certificate for every subdomain, or a wildcard certificate that works for all subdomains (*.example.com). Erik
smime.p7s
Description: S/MIME cryptographic signature
