Ha, I was trying to obscure the actual URL by using example.com, but clearly I screwed up. I might as well paste the unmodified configure.php contents now, which I will do at the bottom. It was late last night - clearly I wasn't with it as I made a couple of other mistakes, see below :-) The problem is still unresolved.
The SSL error you were getting at secure.faircake.co.uk was because of an typo I made when restoring the rewrites/redirects after removing them for testing as mentioned in my earlier post. When restoring the config I accidentally disabled the SSL engine entirely. I have restored SSL, which works fine, as previously mentioned.
The rewrites are both rewrites and redirects. They are rewrites in the sense that they are implemented using Apache's mod_rewrite, via directives RewriteCond and RewriteRule. They are redirects in that they are configured to return a 301 permanent redirect respnse to the client.
In any event the rewrites/redirects are definitely not the source of the problem and can be eliminated from consideration as mentioned in my earlier post. I have tried removing them from the config entirely on both SSL and non-SSL domains, and disabling the rewrite engine altogether. It had no effect on the admin URL problem.
This is going to cause no end of headaches. Redirecting a https request to a http server is a classic setup for an endless loop.
That was just another late-night screw up when typing my post. The redirect is not from https to http, it is from https to https. My config has no redirect loops and in any event I've already verified that the redirects aren't causing the problem by removing them entirely.
As suggested by Schoolboy, get rid of any .htaccess in the ROOT folder. Yes, I/we are aware that you may have been using these rules for many years without any issue, but the fact remains, you do have an issue so these need to be eliminated from the equation until the cause if found. Then, and only then should you consider adding .htaccess rules to cater for specific and/or unusual needs.
As I've already explained in an earlier post, I do not have any .htaccess in the ROOT folder. My rewrite rules are in the main httpd.conf, and again I have tested without those rules present so they are 100% certainly not the cause of the problem.
ps. Always clear your cache files and/or refresh your browser when making any config changes. It is easy to lead yourself astray otherwise (experience speaking).
I have been clearing the cache, cookies, history and all other clear options in Chrome and restarting the browser every time I test this. I am also pretty sure that browser state problems wouldn't be causing admin to build the internal link URLs with the wrong domain name.
Thanks,
Tom
Actual configure.php file contents. Admin:
define('HTTP_SERVER', 'http://www.faircake.co.uk');
define('HTTPS_SERVER', 'https://secure.faircake.co.uk');
define('HTTP_CATALOG_SERVER', 'http://www.faircake.co.uk');
define('HTTPS_CATALOG_SERVER', 'https://secure.faircake.co.uk');
// Use secure webserver for catalog module and/or admin areas?
define('ENABLE_SSL_CATALOG', 'true');
define('ENABLE_SSL_ADMIN', 'true');
Non-Admin:
define('HTTP_SERVER', 'http://www.faircake.co.uk');
define('HTTPS_SERVER', 'https://secure.faircake.co.uk');
// Use secure webserver for checkout procedure?
define('ENABLE_SSL', 'true');
