We've been using the same Turnkey LAMP appliance locally with VirtualBox and this hasn't been an issue before. I haven't changed any of the settings in the files I listed above, but I think I've figured out the issue I'm having. Part of the problem is that I don't have a trusted certificate for my server, because I'm just using the tklapp.com DNS forwarding system. I really like the dynamic DNS though, I see this as a huge convience. I like that I don't have to buy a domain name or just use the IP address of the Amazon EC2 server I'm using.
I'd clicked past the red Chrome warning page on my own machine, but when I sent links to my co-workers to review my progress they showed me it was rendering without any CSS! Getting them to put https:// in the URL of the page fixed the problem, I guess because this forced them to add a security exception to their browsers to continue.
The reason I thought it was "forcing" HTTPS is that some pages weren't loading, or more accurately were giving errors. The issue lies in how the different browsers responded to the cert issue. The Chrome debugger was showing "ILLIGAL TOKEN" error messages for all my included JS files when an http URL was used, and when I viewed the response for those files I was seeing CakePHP error HTML! I believe CakePHP's .htaccess is setup to route 404 errors to cake, so this would explain why I was seeing an HTML error and not a blank page? When I tried to view the page in Firefox, I got an error I couldn't bypass without clicking to accept the cert, and then everything was fine.
After a little tinkering, I figured out that the issue was a few https links in my CakePHP template. When the main page loads via http and the links are https... apparently that's not a good thing. Such a stupid little mistake, and I was looking in the completely wrong place!
Jeremy, thanks for the
Jeremy, thanks for the reply.
We've been using the same Turnkey LAMP appliance locally with VirtualBox and this hasn't been an issue before. I haven't changed any of the settings in the files I listed above, but I think I've figured out the issue I'm having. Part of the problem is that I don't have a trusted certificate for my server, because I'm just using the tklapp.com DNS forwarding system. I really like the dynamic DNS though, I see this as a huge convience. I like that I don't have to buy a domain name or just use the IP address of the Amazon EC2 server I'm using.
I'd clicked past the red Chrome warning page on my own machine, but when I sent links to my co-workers to review my progress they showed me it was rendering without any CSS! Getting them to put https:// in the URL of the page fixed the problem, I guess because this forced them to add a security exception to their browsers to continue.
The reason I thought it was "forcing" HTTPS is that some pages weren't loading, or more accurately were giving errors. The issue lies in how the different browsers responded to the cert issue. The Chrome debugger was showing "ILLIGAL TOKEN" error messages for all my included JS files when an http URL was used, and when I viewed the response for those files I was seeing CakePHP error HTML! I believe CakePHP's .htaccess is setup to route 404 errors to cake, so this would explain why I was seeing an HTML error and not a blank page? When I tried to view the page in Firefox, I got an error I couldn't bypass without clicking to accept the cert, and then everything was fine.
After a little tinkering, I figured out that the issue was a few https links in my CakePHP template. When the main page loads via http and the links are https... apparently that's not a good thing. Such a stupid little mistake, and I was looking in the completely wrong place!