Force https:// to remain as https: no matter what!

I have a site with a SSL and configured the site as https:// > Now that has been set the site either goes to https:// with a diagonal line through https:// or http: and fails to remain https://

The SSL is installed correctly and the site fails to have easy login without clicking on home or  other links first .

Unfortunately I had this same issue when I created site as http:// then changed site to https: ,

So I wiped the site out and started it as https:// from the beginning and have the same issue

htacess  was also modified to accommodate foprcing https:// to remain with no luck

This is because something (an image) isn't loading through https://.  I see a few possible culprits, including the Google Maps block and the ie6nomore.com banner (which is hidden on non-IE6 browsers).

 Does this happen in all browsers?  Open your site in the Google Chrome Browser and left-click on the lock with an red X through it... located next to the https (with a red line through it)... in the URL address bar near the top of the browser.  Does it state the SSL certificate is okay (green icon)?  Does it state the pages source code is linking to insecure data (red icon)?  If the later then you need to go through your source code looking for non-SSL links.  Some Google research on the issue will provide further information.

 I have two Dolphin sites... checking with Chrome,  https is fine in one but not the other (just noticed it today... not sure what happened recently on the D7.0.9 site)... the non-SSL ie6nomore.com link is in both.  Whenever I've had to deal with this issue in the past it was due to an image being loaded from a non-SSL location.  

 After rebooting my computer, the HTTPS failure I mentioned in the above post disappeared.  It appears some Chrome plugin, such as Silverlight, had crashed... rebooting reset and fixed it.  I added an SSL checker plugin to Chrome called SaferChrome Security Report... a nice tool for checking SSL pages.

Ok< so is there a way to force ssl to run http: and not break the https://  ?

As far as I know it's not the http links that are the problem but resources from http locations... such as images that originate from an external site via a http address  In many cases I've found that I can simply convert the http to https (in the code) and it will fix the problem.  If that doesn' t resolve the problem then you might consider other options to move that image to an SSL location.  I have not discovered another way to deal with it... so, I'd have to say "no" there is no way to force ssl to use resources from a non-ssl source without displaying a warning.

As I mentioned before... you could try using Google Chrome browser with the SaferChrome Security plugin to get some feedback on which links within an SSL page are insecure.

I found a solution to some of my issues, but here is another question  about dolphin and htaccess. Dolphin has several htacces within it. Will dolphin still function if all the htaccess records are updated to https:// ?

to get the ssl to lock in, I thought I had the resolution, but I still have issues and still looking for answers to force ssl to remain locked in with all browsers. dolphin has hard coded http:// in to script which need to be changes to https://

I just copy pasted the solution may it help i make a little search for it.

Sometimes you may need to make sure that the user is browsing your site over secure connection. An easy to way to always redirect the user to secure connection (https://) can be accomplished with a .htaccess file containing the following lines:

RewriteEngine On 
RewriteCond %{SERVER_PORT} 80 
RewriteRule ^(.*)$ https://www.example.com/$1 [R,L]

Please, note that the .htaccess should be located in the web site main folder.

In case you wish to force HTTPS for a particular folder you can use:

RewriteEngine On 
RewriteCond %{SERVER_PORT} 80 
RewriteCond %{REQUEST_URI} somefolder 
RewriteRule ^(.*)$ https://www.domain.com/somefolder/$1 [R,L]

The .htaccess file should be placed in the folder where you need to force HTTPS.

I had done this  along time ago and still have issues. The site will not lock down 100% all the time

RewriteEngine On 
RewriteCond %{SERVER_PORT} 80 
RewriteRule ^(.*)$ https://www.domain.com/somefolder/$1 [R,L]