I think this could help:

http://jondjones.com/learn-episerver-cms/episerver-developers-guide/episerver-security/how-to-make-your-episerver-website-run-via-https

Links within CMS is normally stored in an internal format (guid based) that is not absolute. The outgoing links are generated at runtime so it should be fine to change schema for normal links.

You do not need this since as Johan says, the links are not stored with https or http.

The only thing you need to do is to search all your files for hardcoded links to for examle js-files where you us http:// instead of just // (where it is supported)

You might also need to go through the database so search for where your editors has added hard coded links within tiny editor or in any other link place.

This is a simple and quick SQL-skript that will gives you all the rows where there are http:// links  and most of them are propably fine if you do not use them to for example write out a css-file or an iFrame.

Select fkOwnerContentID, LinkURL
From tblContentSoftlink 
Where LinkURL like 'http://%'

Select fkContentID, LongString
From tblContentProperty
Where LongString like '%http://%'

That config above does not work properly with redirection with parameter in query. Below is what we use currently:

<rule name="HTTP/S to HTTPS Redirect" enabled="true" stopProcessing="true">
          <match url="(.*)" />
          <conditions logicalGrouping="MatchAny">
            <add input="{SERVER_PORT_SECURE}" pattern="^0$" />
          </conditions>
          <action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
</rule>

you can have just this in conditions:

<conditions>
    <add input="{HTTPS}" pattern="off" ignoreCase="true" />
</conditions>