Apache SSL setup for wildcard domains

[chris]

I just got the latest peepcode video on Apache configuration, hoping
that it would solve a few problems I was having. Although after only
watching a small part of the video I have learned a couple things, but
my main issue is still unanswered.

I have a site that allows for clients to have their own subdomains.
Getting the one wildcard SSL certificate to work was an issue. What I
need is to be able to configure Apache to automatically accept new
domains without me having to manually enter the new subdomain when
someone signs up. Can this be done? In one place I read that it can
be done if you set the Common Name to *.my_domain, unfortunately I
could not get it to work.

If you anyone can shed some light on this I would really appreciate
it.

Thanks

[topfunky]

On Jul 5, 7:13 am, chris <olsen.ch...@gmail.com> wrote:
> I have a site that allows for clients to have their own subdomains.

In my experience, Apache serves up the first virtual host for any
unknown domains. Define the app that will handle the subdomains as the
first virtual host and they should be sent to that Rails app.

In your current configuration, what happens when you try to visit an
unknown subdomain?

Geoffrey Grosenbach
http://peepcode.com

[chris]

> In my experience, Apache serves up the first virtual host for any
> unknown domains. Define the app that will handle the subdomains as the
> first virtual host and they should be sent to that Rails app.

Do you set the common name to *.domain_name or just the domain_name?

> In your current configuration, what happens when you try to visit an
> unknown subdomain?

Nothing, but I am unsure if that was because the Common Name was set
improperly. I need to get apache set up on my dev machine to more
easily play with it.

>
> Geoffrey Grosenbachhttp://peepcode.com

[Linda Derezinski]

use *.example.com. Then to force that VirtualHost record to be loaded
first I use 001-example.com.conf for the name of the virtualhost
configuration file.
-Linda