Quote from: nickf08 at Nov 02, 2017, 10:05 PMIt was a crap host. Finally changed to a great new host and https working easily as expected
I know this is resurrecting and old thread, but I find this solution to be incomplete. The problem here is how evolution handles the header requests, in particular when it is behind a reverse proxy. Many hosts, and many instances require a reverse proxy where the SSL certificate is provided by the reverse proxy, and the website itself is hosted on a machine behind the proxy that doesn't have a cert and is only served to the proxy via http. I am running in to a similar issue on a current build, and it seems that the recent iterations of evolution still have not resolved this issue. Essentially there should be a way of over-riding the detected incoming header information and forcing the site to use https in all the url creation processes. Right now it seems that the detected incoming header of the requests is used to override any site-side settings. This is extremely frustrating. I did find one reference to setting the proxy_pass method to "Set Cookie"; in Apache which has worked for some, but i am using a non-standard reverse proxy (Caddy) that doesn't have a setting for that that I can find. In general there should be a way to simply override this on the site site as fairly simple solution, but that doesn't seem to exist.
