SSL

[Guest]

// Define the webserver and path parameters

// * DIR_FS_* = Filesystem directories (local/physical)

// * DIR_WS_* = Webserver directories (virtual/URL)

define('HTTP_SERVER', 'http://micomputer.net'); // eg, http://localhost - should not be empty for productive servers

define('HTTPS_SERVER', 'https://micomputer.net'); // eg, - should not be empty for productive servers

define('ENABLE_SSL', 1); // secure webserver for checkout procedure?

define('HTTP_COOKIE_DOMAIN', 'micomputer.net');

define('HTTPS_COOKIE_DOMAIN', 'micomputer.net');

define('HTTP_COOKIE_PATH', '/catalog/');

define('HTTPS_COOKIE_PATH', '/catalog');

define('DIR_WS_HTTP_CATALOG', '/catalog/');

define('DIR_WS_HTTPS_CATALOG', '/catalog/');

define('DIR_WS_IMAGES', 'images/');

define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');

define('DIR_WS_INCLUDES', 'includes/');

define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');

define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');

define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');

define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');

define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');

 

define('DIR_WS_DOWNLOAD_PUBLIC', 'pub/');

define('DIR_FS_CATALOG', '/home/ostin/domains/micomputer.net/public_html/catalog/');

define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');

define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');

 

// define our database connection

define('DB_SERVER', 'localhost'); // eg, localhost - should not be empty for productive servers

 

 

 

 

this is my configure.php file my ssl server is https://micomputer.net

but when i set the ssl server like this not working what can i do?

 

 

sorry for bad english :)

[FalseDawn]

Do you have a dedicated SSL Cert installed for https://micomputer.net?

 

Looks like it might have been installed for https://www.micomputer.net? In which case, you'll need to change your configure files to reflect this.

[Guest]

you can not use an ssl certificate you have generated on your own server, as your server is not a trusted ssl certificate issuer. you need to purchase from a known trusted supplier.

 

from your ssl certificate:

 

issuded to: localhost.localdomain

 

issued by: localhost.localdomain

[Guest]

you can not use an ssl certificate you have generated on your own server, as your server is not a trusted ssl certificate issuer.  you need to purchase from a known trusted supplier.

 

from your ssl certificate:

 

issuded to: localhost.localdomain

 

issued by:  localhost.localdomain

<{POST_SNAPBACK}>

 

Not strictly true. You could use a self generated server certificate, as long as you create it with the correct domain name.

 

The only problem is that the browser will complain about the issuing company and ask for confirmation, but the SSL still works in exactly the same way as one from a 'trusted' authority, you still have the same level of encryption. Only difference being is browsers have most 'trusted' authorities already setup within them so no warning pops up.

 

All of this is to do with Customer perception, will the customer accept that a certificate issued by Joe Bloggs Co for www.joebloggs.com is safe? maybe, maybe not.

 

That is the only reason to use a 'trusted' authority, because they have verified that you are the company you say you are before issuing a certificate. They also provide some type of indemnity I believe