Better errors when using non-https servers
Right now, it's fairly opaque that it implicitly adds an https://
to the front of the URL.
Some ideas:
- Better UX to show that it's https
- Better error if it's http but it attempts to connect to https. This will throw an
SSLError
, so it should be easy to catch. - From @robozman: You could have a little button to the left of the URL box that specifies http or https and has a lock icon or whatever and when you type the scheme in the box is updates that box.
Edited by Sumner Evans