Configuring HTTPS

Configuring HTTPS

am 29.12.2007 03:22:16 von Aaron Gray

Okay, got a SSL certificate now, found out I can only have one HTTPS named
virtual server which is a sh*t.

Now anyone tell me how to make Apache force/only use HTTPS for shtml file
serving and not allow HTTP to access .shtml files ?

Many tanks in advance,

Aaron

Re: Configuring HTTPS

am 29.12.2007 13:35:54 von unknown

Post removed (X-No-Archive: yes)

Re: Configuring HTTPS

am 30.12.2007 00:15:38 von Aaron Gray

"Davide Bianchi" wrote in message
news:slrnfncfq5.37f.davideyeahsure@fogg.onlyforfun.net...
> On 2007-12-29, Aaron Gray wrote:
>> Okay, got a SSL certificate now, found out I can only have one HTTPS
>> named
>> virtual server which is a sh*t.
>
> Incorrect, you can have as many as you want, but all of them will use
> the same certificate. That's inherent in the way HTTPS works.

So the certificate provider should be ble to provide me with a SSL
certificate that will work for multiple domains ?

>> Now anyone tell me how to make Apache force/only use HTTPS for shtml file
>> serving and not allow HTTP to access .shtml files ?
>
> Use a block to disallow access in the http vhost and/or
> use a Rewrite rule or Redirect to redirect to https.
>
> Something like
>
>
> Order allow,deny
> Deny from all
>

>
> RewriteCond %{REQUEST_URI} .*\.shtml$
> RewriteRule ^/(.*)$ https://..../$1

I will have to decypher this, its a bit cryptic.

Thanks,

Aaron

Re: Configuring HTTPS

am 30.12.2007 08:42:10 von unknown

Post removed (X-No-Archive: yes)

Re: Configuring HTTPS

am 30.12.2007 14:39:55 von Aaron Gray

"Davide Bianchi" wrote in message
news:slrnfneivf.356.davideyeahsure@fogg.onlyforfun.net...
> On 2007-12-29, Aaron Gray wrote:
>>> Incorrect, you can have as many as you want, but all of them will use
>>> the same certificate. That's inherent in the way HTTPS works.
>>
>> So the certificate provider should be ble to provide me with a SSL
>> certificate that will work for multiple domains ?
>
> You can have a certificate for the domain (*.domain.com), but it will
> cost you a fortune and the browsers will still complains that
> "the certificate belongs to a different server" (or similar, don't
> remember the real error message), if that doesn't bother you, it's ok.
> It all depends on what you want, if you want encryption, it's fine.

Thats called a wildcard certificate.

There are MDC (Multiple Domain Certificates). These are both availiable from
:-

http://www.positivessl.com

Aaron