Forcing the use of https

[teefers (Doug Bennett)]

There’s all kinds of post on https on the forum searching you would find a bunch.
Here’s some that might help.

This post shows you some htaccess rules that don’t require your URL:

No padlock on move to https

Looking at the URL to the page you gave above there are only about 15 or so images referenced on that page. WhyNoPadlock only checks one page at a time. The mixed content warnings you are getting (from WhyNoPadlock) are “soft” warnings and should be fixed but shouldn’t stop you from implementing the SSL. Only active mixed content (things that change a page like Javascript or CSS) will "break a site. I would check the other pages before working on the redirects. The redirect isn’t working…

RW8 has a built in feature to edit the htaccess file. This post shows a video on how to use:

Footer links to privacy policy page not working

This post will give you an htaccess rule to move from HTTP to HTTPS. This is a video from Ben at RealMac on how to use the new (RW8) htaccess editor built in. [RapidWeaver 8 htaccess File Editing]

This post explains more for pre RW8

My site shows up as not secure

That goes into the htaccess file. In RapidWeaver 8 in publishing settings, at the bottom is an edit htaccess button( I think that’s what it’s called not at a Mac now). You can also use any ftp client to upload it to the root level of the site. It has to be PLAIN text, and called .htaccess . Fix the mixed content first. Especially if it’s active content or it can break the site. Once you’re using https all active content has to be https.