Enabled SSL

[marcoren]

The user logs in succesfully but the redirect fails:

 

https://mywebsite.com/catalog/login.php/action/process

 

 

My configure.php looks like this:

 

define('HTTP_SERVER', 'http://www.mywebsitecom');

define('HTTPS_SERVER', 'https://www.mywebsite.com/catalog/');

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

define('HTTP_COOKIE_DOMAIN', 'www.mywebsitecom');

define('HTTPS_COOKIE_DOMAIN', 'www.mywebsite.com');

define('HTTP_COOKIE_PATH', '/');

define('HTTPS_COOKIE_PATH', '/');

 

 

 

Should the login be SSL protected? I thought it was just the checkout procedure?

[AlanR]

The user logs in succesfully but the redirect fails:

 

https://mywebsite.com/catalog/login.php/action/process

My configure.php looks like this:

 

  define('HTTP_SERVER', 'http://www.mywebsitecom');

  define('HTTPS_SERVER', 'https://www.mywebsite.com/catalog/');

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

  define('HTTP_COOKIE_DOMAIN', 'www.mywebsitecom');

  define('HTTPS_COOKIE_DOMAIN', 'www.mywebsite.com');

  define('HTTP_COOKIE_PATH', '/');

  define('HTTPS_COOKIE_PATH', '/');

Should the login be SSL protected?  I thought it was just the checkout procedure?

<{POST_SNAPBACK}>

 

Log in is protected but we need the next few lines of the config file to see if what you posted is correct.

[marcoren]

The rest of my config file says:

 

define('DIR_FS_DOCUMENT_ROOT', '/mywebsite.com/');

define('DIR_FS_LOGS', '/logs/mywebsite.com');

 

// define our database connection

define('DB_SERVER', 'mysql./mywebsite.com');

define('DB_SERVER_USERNAME', '');

define('DB_SERVER_PASSWORD', '');

define('DB_DATABASE', 'oscommerce');

define('CONFIGURE_STATUS_COMPLETED', 1);

define('USE_PCONNECT', 'false');

define('STORE_SESSIONS', 'mysql');

?>

[AlanR]

You left out these, the ones I wanted to see.

 

define('DIR_WS_HTTP_CATALOG', '');

define('DIR_WS_HTTPS_CATALOG', '');

[marcoren]

Alan,

 

I don't have those set. When I include them, it breaks my site. What, do you suggest I set them as?

 

Thank you,

Marc

[AlanR]

Alan,

 

I don't have those set.  When I include them, it breaks my site.  What, do you suggest I set them as?

 

Thank you,

Marc

<{POST_SNAPBACK}>

 

To work with the lines you posted in your first post they would be:

 

define('DIR_WS_HTTP_CATALOG', 'catalog');

define('DIR_WS_HTTPS_CATALOG', '/');

 

 

and I'd change this line:

 

define('HTTPS_COOKIE_DOMAIN', 'www.mywebsite.com');

 

to

 

define('HTTPS_COOKIE_DOMAIN', 'www.mywebsite.com/catalog');

 

Think about what osC has to do. It has to add these strings together to get to the right place depending on what's requested.

 

It's actually pretty simple, you could do it on a piece of paper.

[marcoren]

Alan,

 

Thanx for the help. It turns out that I needed them to be in sync.

 

What I mean is, my http server and https server weren't matching so then redirects were getting confusing. Once I made them match, everything works.

 

define('HTTP_SERVER', 'http://www.mywebsitecom/catalog');

define('HTTPS_SERVER', 'https://www.mywebsite.com/catalog');

 

define('DIR_WS_HTTP_CATALOG', '/');

define('DIR_WS_HTTPS_CATALOG', '/');

 

 

Thank you,

Marc

[AlanR]

Alan,

 

Thanx for the help.  It turns out that I needed them to be in sync.

 

What I mean is, my http server and https server weren't matching so then redirects were getting confusing.  Once I made them match, everything works.

 

Thank you,

Marc

<{POST_SNAPBACK}>

 

Well, that will work but the "Top" link will take you to the catalog and not to your homepage/

 

It's more common (and standard) to have:

 

define('HTTP_SERVER', 'http://www.mywebsitecom');

define('HTTPS_SERVER', 'https://www.mywebsite.com');

 

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

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

 

There was a post a couple days ago with a shared ssl server where

 

define('HTTPS_SERVER', 'https://www.mywebsite.com');

 

had to be

 

define('HTTPS_SERVER', 'https://www.mywebsite.com/catalog');

 

because of a whacky ssl set up but that's unusual.