SSL - admin login page browser warning

[Crunch]

I've had a working zen cart installation for months. Slowly adding products, testing and playing around before I cutover from an existing non-ecommerce site. I am now at the point of testing payment and therefore have just recently ordered a SSL certificate from my host. The SSL was installed and I can access my domain with https.

I went to the store's admin logon page with https and after I put in my username and password and click the Login button, I receive the following browser error:

Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party.

Are you sure you want to continue sending this information?

I hit the continue button and I am taking into my admin panel but, it's not secured.

I followed the tutorials for enabling SSL in zen cart. Here are my configure files.

Here is my includes/configure.php:

// Define the webserver and path parameters
  // HTTP_SERVER is your Main webserver: eg-http://www.your_domain.com
  // HTTPS_SERVER is your Secure webserver: eg-https://www.your_domain.com
  define('HTTP_SERVER', 'http://www.mydomainname.com');
  define('HTTPS_SERVER', 'https://www.mydomainname.com');

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

Here is my admin/includes/configure.php:

   * If you desire your *entire* admin to be SSL-protected, make sure you use a "https:" URL for all 4 of the following:
   */
  define('HTTP_SERVER', 'http://www.mydomainname.com');
  define('HTTPS_SERVER', 'https://www.mydomainname.com');
  define('HTTP_CATALOG_SERVER', 'http://www.mydomainname.com');
  define('HTTPS_CATALOG_SERVER', 'https://www.mydomainname.com');

  // Use secure webserver for catalog module and/or admin areas?
  define('ENABLE_SSL_CATALOG', 'true');
  define('ENABLE_SSL_ADMIN', 'true');

So, not sure why the admin logon page shows it's secure in browser but, when I hit the Login button, it gives me the warning and then the admin pages are not secure.

[Crunch]

OK. Maybe I figured this out.

I added https to HTTP_SERVER and HTTP_CATALOG_SERVER in the admin/includes/configure.php

The browser security error has gone away and the admin panel is secure as far as I can tell.

* If you desire your *entire* admin to be SSL-protected, make sure you use a "https:" URL for all 4 of the following:
   */
  define('HTTP_SERVER', 'https://www.mydomainname.com');
  define('HTTPS_SERVER', 'https://www.mydomainname.com');
  define('HTTP_CATALOG_SERVER', 'https://www.mydomainname.com');
  define('HTTPS_CATALOG_SERVER', 'https://www.mydomainname.com');

  // Use secure webserver for catalog module and/or admin areas?
  define('ENABLE_SSL_CATALOG', 'true');
  define('ENABLE_SSL_ADMIN', 'true');

[Ajeh]

That is masking the problem ... what you have done is make the whole admin run secure rather than find what is not secure when running secure ...

[Crunch]

Well, I don't know what's going on now but, after reading your reply I thought I would set it back to the way I had it after enabling SSL. I would of expected the browser security warning would have appeared again when accessing the admin panel but, it doesn't. I am baffled but, here is how I have the configure file now. Think I am OK now and not masking any issue (I hope)

admin/includes/configure.php:

   * If you desire your *entire* admin to be SSL-protected, make sure you use a "https:" URL for all 4 of the following:
   */
  define('HTTP_SERVER', 'http://www.mydomainname.com');
  define('HTTPS_SERVER', 'https://www.mydomainname.com');
  define('HTTP_CATALOG_SERVER', 'http://www.mydomainname.com');
  define('HTTPS_CATALOG_SERVER', 'https://www.mydomainname.com');

  // Use secure webserver for catalog module and/or admin areas?
  define('ENABLE_SSL_CATALOG', 'true');
  define('ENABLE_SSL_ADMIN', 'true');

[Ajeh]

At best a guess ... it looks right ... but I cannot tell if you might have typos or not in the real configure.php files on the sever so if it appears to work for you in both FireFox and IE ... then there is a good chance that you have done this correctly ...