Mixed Domains in a Local Server

This topic applies to

Applies to

SuiteCommerce | SuiteCommerce Advanced


When redirecting between domains while testing on your local server, the default behavior is for the application to load the production version of the initial page in the new domain.

For example, suppose you start in the local version of the Shopping domain using the shopping-local.ssp URL. On login, you are redirected to the production version of the Checkout domain at the my-account.ssp URL. To return to the local version of that domain you must manually edit the URL.

Change: https://checkout.netsuite.com/c.xxxxxxx/sca-dev-denali/my_account.ssp?n=3
To: https://checkout.netsuite.com/c.xxxxxxx/sca-dev-denali/my_account-local.ssp?n=3

Also, in some browsers, when you manually update this URL you may encounter blank page loads with console errors similar to the following:

Mixed Content: The page at 'https://checkout.netsuite.com/c.xxxxxx/sca-dev-denali/my_account-local.ssp?n=3' was loaded over HTTPS, but requested an insecure stylesheet 'http://localhost:7777/css/myaccount.css'. This request has been blocked; the content must be served over HTTPS.

For example, Chrome returns this error to protect you from a site that is not secure. If this happens in Chrome, in the address bar you will see a shield. Click on the shield and select Load unsafe scripts. The page then loads normally.


You can also launch the Chrome browser with the flag --allow-running-insecure-content or you can install the certificates in your local web server.