I'm going to register an SSL certificate and a merchant account tomorrow. I have a question about the SSL certificate.

Well, the link for my billing system is

"http://www.midpulse.com/support"

When signing up for the SSL certificate, should I register it for

"http://www.midpulse.com"

or

"http://www.midpulse.com/support"

Just for http://midpulse.com

Just for http://midpulse.com

That will then cover things like /support or /billing etc.

Best of luck with it all.

Just for http://midpulse.com

Ahh thank you. One last question.

Should I register it for

"http://www.midpulse.com"

or

"http://midpulse.com"

because I heard there was a difference

http://www.midpulse.com that will cover all of your bases

where are you getting your ssl cert?

http://www.midpulse.com that will cover all of your bases

ahh thank you :)

and i'm getting it from enom

Ahh thank you. One last question.

Should I register it for

"http://www.midpulse.com"

or

"http://midpulse.com"

because I heard there was a difference


If your visitors are primarily on the www.midpulse.com address, then register an SSL for that domain name. However, if your users typically omit the 'www', then get an SSL cert just for midpulse.com. What you want to avoid are 'Security Certificate Mismatch' pop-up errors.

You may want to even consider registering secure.midpulse.com in your SSL certificate. Some companies have opted to do so just to make it clear to their clients when they are on a secure portion of their site and when they are not on a secure portion of their site.

And make sure to use .htaccess to force your users to the one you secure. If you get the ssl with www., force your users to access the site using www.

And make sure to use .htaccess to force your users to the one you secure. If you get the ssl with www., (http://www.,) force your users to access the site using www.

Alright, I'll look into that. Thank you.

One last question, sorry :P

When signing up for the SSL..it asks for the server type. It's apache, and it gives apache choices, but one of the choices is also cpanel..should I choose cpanel of that's what we use?

Alright, I'll look into that. Thank you.




Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^domain.com [NC]
RewriteRule ^(.*)$ http://www.domain.com/$1 [L,R=301]

Just add that to .htaccess and it will redirect the http://domain.com to http://www.domain.com

you can also consider a wild card cert that will cover any sub domain and the main domain.

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^domain.com [NC]
RewriteRule ^(.*)$ http://www.domain.com/$1 [L,R=301] Just add that to .htaccess and it will redirect the http://domain.com to http://www.domain.com

Ohh thank you! :)

Would I have to edit the htaccess in every directory with that?

No, just your root directory. .htaccess works recursively.