Digital Certificate Basics

I'm getting these errors & I'm not sure what to do...

[newnewbie1]

Hi!

I'm trying to load a new form into the folder that is configured for our digital certificate... I'm having some problems...

1st I got the message about "You are trying to display both secure and nonsecure items, would you like to proceed?" It was having a problem with my gif files saying they were non-secure. So I referenced them with an HTTPS.

Question #1 - is that necessary?

Now I'm getting an error message saying " The name on the security certificate is invalid or does not Match the Site Name"

Question #2 - What could that be?

[The Contractor]

Hmm. are you calling the page/form through a link like https://domain.com/page.htm and not like https://www.domain.com/page.htm?
Sounds like you are placing www within the url/link which will give you that error.

[Gorufu]

I'm trying to load a new form into the folder that is configured for our digital certificate... I'm having some problems...

Assuming you purchased a certificate for yourdomain.com I find it strange that a separate folder would be configured for your SSL server.

1st I got the message about "You are trying to display both secure and nonsecure items, would you like to proceed?" It was having a problem with my gif files saying they were non-secure. So I referenced them with an HTTPS.

Question #1 - is that necessary?

No it's not necessary if you use relative links to your images.
eg <img src="images/image.gif">
The images may need to be within your secure folder to avoid problems.

Now I'm getting an error message saying " The name on the security certificate is invalid or does not Match the Site Name"

Question #2 - What could that be?

If the domain on the certificate is www.domain.com the URL will need to be [domain.com...] In this example [domain.com...] would not match and produce a pop-up warning.

Naturally the reverse would be true if the domain name on the certificate is domain.com without the www

[dingman]

I find it strange that a separate folder would be configured for your SSL server.

<VirtualHost oneofmydomains.tld:80>
DocumentRoot /var/www/oneofmydomains-nossl
... other directives ...
</VirtualHost>
<VirtualHost oneofmydomains.tld:443>
DocumentRoot /var/www/oneofmydomains
SSLEngine on
SSLCertificateFile /path/to/cert
SSLCertificateKeyFile /path/to/key
... other directives ...
</VirtualHost>

Separate content, separate folders.

[Gorufu]

Hi Dingman,

I know how to setup different directories for SSL vhosts but it can lead to confusion and problems as experienced by the original poster, newnewbie1

I fail to see any advantages in having separate directories and content when customers are prepared to purchase their own certificate.

[dingman]

It's not in place at the moment, but I intend eventually to switch my family site over so that my-family.tld:80 is the publicly accessible family vanity page, and my-family:443 is the limited-access family site with some real utility to it. Right now the latter doesn't exist and its document root is just a symlink to the vanity page dorcument root. However, it seems much cleaner to me than a subdirectory for the stuff you want to keep secure.