@rugk Supporting both HTTP and HTTPS would be terrible because that defeats the purpose of HTTPS. However, allowing upgrades from HTTP to HTTPS is something I've already put some code in place for but it doesn't seem to reach quite all the way yet.

The reason it's a problem is that the web (as in how it's defined by the W3C) uses URIs and these URIs cannot change because then it's a _new_ URI and can (and probably does) identify a new resource.