BUG: https will work now

http:// was getting added to the beginning of https:// urls, causing the
remote to be expanded arbitrarily to http://https:// when the user
entered a remote that was https