On 27/02/07, Bill Walton <[EMAIL PROTECTED]> wrote:
> As I understand it, I need 'single' cert for my app, but will want / need a
> 'wildcard' cert to handle the subdomains. My question is: can I start with
> a single cert for my domain and later 'upgrade' that to the wildcard
> version? Or will I replace the single with the wildcard? Or will I have
> dug myself into a hole by starting with a single? Also, in the subdomains,
> will it be possible to serve portions in secure mode and others in
> non-secure?
If you're using www.myapp.com as well as #{customername}.myapp.com,
you need a wildcard cert. If you have a single cert for www.myapp.com,
you'll get warnings from the browser as soon as they try to access
#{customername}.myapp.com.
You can serve whatever you want using http, https or a combination of
both. link_to lets you select the protocol to use. The only thing to
be aware of is that browsers tend to throw up warnings when you try to
pull in http content into a page that was served over https.
Cheers,
Gareth
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---
