Hi, Using https://application.oursite.com/ would imho be the only simpel solution. An SSL certificate is IP bound, and if you are to serve plain and secure on 1 domain name, you're in for an administrative nightmare.
https://www.oursite.com/application/ is possible but then you need to keep track where requests are served (port 80 or port 443). rewriting urls from and to (e.g. apaches mod_rewrite) is possible but again it's easier for security mistakes to sneak in. Then if your pagehits are not enormously high why wouldn't you put it all on SSL. It's easier to maintain, and SSL performance issues are not in sight until you reach 1000's of hits (or more) a sec. Hope it helps. Regards, Gerard. [EMAIL PROTECTED] wrote: > We have an online application for school, where we request the > individuals SSN and PharmCAS information. The application will be at > say www.oursite.com/application/. Since we're gathering sensitive > data, I want to obviously make this secure using https:// I don't want > the rest of the site to be on secure, just the online app part of the > site. What would be the best way to do this? Create a subdomain, > https://application.oursite.com/ or can I just secure > https://www.oursite.com/application/ ? > > thnx, > > -- urls = { 'fun': 'www.zonderbroodje.nl', 'tech': 'www.gp-net.nl' } --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
