In SSL Front Page can not connect with stylesheet and images

[Okanya]

See. Problem is, something within the following assignment is true such that $request_type is set to SSL. The test run by ZC is considered to be general enough to not miss that a site is setup to permit/show the content over a secure method, but also may misinterpret some signals because of the way the host has setup their system.

Basically if any one of these following sections is true (code is from includes/init_includes/init_file_db_names.php) then the software will attempt to present the page using https.

$request_type = (((isset($_SERVER['HTTPS']) && (strtolower($_SERVER['HTTPS']) == 'on' || $_SERVER['HTTPS'] == '1'))) ||
                 (isset($_SERVER['HTTP_X_FORWARDED_BY']) && strpos(strtoupper($_SERVER['HTTP_X_FORWARDED_BY']), 'SSL') !== false) ||
                 (isset($_SERVER['HTTP_X_FORWARDED_HOST']) && (strpos(strtoupper($_SERVER['HTTP_X_FORWARDED_HOST']), 'SSL') !== false || strpos(strtolower($_SERVER['HTTP_X_FORWARDED_HOST']), str_replace('https://', '', HTTPS_SERVER)) !== false)) ||
                 (isset($_SERVER['HTTP_X_FORWARDED_SERVER']) && strpos(strtolower($_SERVER['HTTP_X_FORWARDED_SERVER']), str_replace('https://', '', HTTPS_SERVER)) !== false) ||
                 (isset($_SERVER['SCRIPT_URI']) && strtolower(substr($_SERVER['SCRIPT_URI'], 0, 6)) == 'https:') ||
                 (isset($_SERVER['HTTP_X_FORWARDED_SSL']) && ($_SERVER['HTTP_X_FORWARDED_SSL'] == '1' || strtolower($_SERVER['HTTP_X_FORWARDED_SSL']) == 'on')) ||
                 (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && (strtolower($_SERVER['HTTP_X_FORWARDED_PROTO']) == 'ssl' || strtolower($_SERVER['HTTP_X_FORWARDED_PROTO']) == 'https')) ||
                 (isset($_SERVER['HTTP_SSLSESSIONID']) && $_SERVER['HTTP_SSLSESSIONID'] != '') ||
                 (isset($_SERVER['HTTP_X_FORWARDED_PORT']) && $_SERVER['HTTP_X_FORWARDED_PORT'] == '443') ||
                 (isset($_SERVER['SERVER_PORT']) && $_SERVER['SERVER_PORT'] == '443')) ? 'SSL' : 'NONSSL';

Recently seen is when a host has setup a proxy server and haven't properly setup variables/constants correctly such as HTTP_X_FORWARDED_BY and having it set such that it is the same content as what is used for connecting to the https server. Problem is, that when there is no SSL assigned to the site, then that should not evaluate to be true. It could be other such comparisons, but there is a thread around here that describes how to setup a file to put on your server, tell your host to access the file and either explain why or correct the server settings until all is right.

But the "quick" fix would be to modify your HTTPS_SERVER setting in the includes/configure.php file as already suggested.
Would also agree to use false instead of the pair of single quotes just for consistency to the concept that is generally addressed as a boolean and the instruction of using true or false not true and left empty or something similar.

Thanks. I have just checked the files and applied as informed , but still not change.
Fast ssl is possible to have one but just to understand from what reason ZC has this problem for possible user who would face such problem.
My files are as below;
includes/init_includes/init_file_db_names.php
$request_type = (((isset($_SERVER['HTTPS']) && (strtolower($_SERVER['HTTPS']) == 'on' || $_SERVER['HTTPS'] == '1'))) ||
(isset($_SERVER['HTTP_X_FORWARDED_BY']) && strpos(strtoupper($_SERVER['HTTP_X_FORWARDED_BY']), 'SSL') !== false) ||
(isset($_SERVER['HTTP_X_FORWARDED_HOST']) && (strpos(strtoupper($_SERVER['HTTP_X_FORWARDED_HOST']), 'SSL') !== false || strpos(strtolower($_SERVER['HTTP_X_FORWARDED_HOST']), str_replace('https://', '', HTTPS_SERVER)) !== false)) ||
(isset($_SERVER['HTTP_X_FORWARDED_SERVER']) && strpos(strtolower($_SERVER['HTTP_X_FORWARDED_SERVER']), str_replace('https://', '', HTTPS_SERVER)) !== false) ||
(isset($_SERVER['SCRIPT_URI']) && strtolower(substr($_SERVER['SCRIPT_URI'], 0, 6)) == 'https:') ||
(isset($_SERVER['HTTP_X_FORWARDED_SSL']) && ($_SERVER['HTTP_X_FORWARDED_SSL'] == '1' || strtolower($_SERVER['HTTP_X_FORWARDED_SSL']) == 'on')) ||
(isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && (strtolower($_SERVER['HTTP_X_FORWARDED_PROTO']) == 'ssl' || strtolower($_SERVER['HTTP_X_FORWARDED_PROTO']) == 'https')) ||
(isset($_SERVER['HTTP_SSLSESSIONID']) && $_SERVER['HTTP_SSLSESSIONID'] != '') ||
(isset($_SERVER['HTTP_X_FORWARDED_PORT']) && $_SERVER['HTTP_X_FORWARDED_PORT'] == '443') ||
(isset($_SERVER['SERVER_PORT']) && $_SERVER['SERVER_PORT'] == '443')) ? 'SSL' : 'NONSSL';

includes/configure.php
define('HTTP_SERVER', 'http://www.bakkerijmachines.net');
define('HTTPS_SERVER', 'https://www.bakkerijmachines.net');

/**
* If you want to tell Zen Cart to use your HTTPS URL on sensitive pages like login and checkout, set this to 'true'. Otherwise 'false'. (Keep the quotes)
*/
define('ENABLE_SSL', '');

Awaiting professionals for advises

Thanks in advance

[lat9]

@Okanya, are you really, really sure that you made that update to /includes/configure.php, setting

define ('ENABLE_SSL', 'false');

Zen Cart will set that file to be read-only, so you normally have to change the file's permissions back to read/write before applying those changes.

[mc12345678]

@Okanya, are you really, really sure that you made that update to /includes/configure.php, setting

define ('ENABLE_SSL', 'false');

Zen Cart will set that file to be read-only, so you normally have to change the file's permissions back to read/write before applying those changes.

Be sure to apply one change at a time, then test. Typical permission settings to make a change need to be 644 or 0644 if four digits are shown. ZC will protect the file typically by setting the permissions to 444 or 0444.
1. Please change the permissions to allow writing. (this can often be done within your ftp program or a file manager from your host.)
2. Modify the includes/configure.php to have

define ('ENABLE_SSL', 'false');

.
3. After making the change, reopen the file to verify that the change was saved.
4. Clear your cache or go to a different browser/computer that hasn't tried in a while and go to your page (or tell us here that the change has been made).
5. If it works, then solution likely found, but may still need to work with the host. If not, please try the other suggestion of modifying the HTTPS_SERVER constant to:

define ('HTTPS_SERVER', 'http://www.bakkerijmachines.net');

Notice the removal of the s from the right side address in https://www.bakkerijmachines.net.

[Okanya]

Be sure to apply one change at a time, then test. Typical permission settings to make a change need to be 644 or 0644 if four digits are shown. ZC will protect the file typically by setting the permissions to 444 or 0444.
1. Please change the permissions to allow writing. (this can often be done within your ftp program or a file manager from your host.)
2. Modify the includes/configure.php to have

define ('ENABLE_SSL', 'false');

.
3. After making the change, reopen the file to verify that the change was saved.
4. Clear your cache or go to a different browser/computer that hasn't tried in a while and go to your page (or tell us here that the change has been made).
5. If it works, then solution likely found, but may still need to work with the host. If not, please try the other suggestion of modifying the HTTPS_SERVER constant to:

define ('HTTPS_SERVER', 'http://www.bakkerijmachines.net');

Notice the removal of the s from the right side address in https://www.bakkerijmachines.net.

Modification as below,solved the problem. I will keep you informed .
define ('HTTPS_SERVER', 'http://www.bakkerijmachines.net');
Thanks for all suggestions and your time.

[mc12345678]

Modification as below,solved the problem. I will keep you informed .
define ('HTTPS_SERVER', 'http://www.bakkerijmachines.net');
Thanks for all suggestions and your time.

One can assume it was done, but it's better to know. Please confirm that the define for SSL_ENABLE now has the word false in it and it is not just an empty set of single quotes.

Glad that this has temporarily been corrected, but understand that without working with your host further on this issue that when/if you obtain a SSL that you will likely have to change both HTTP_SERVER and HTTPS_SERVER to start with https: in order for all to work properly. So make note of this thread.