Closed ramack closed 5 years ago
@voriondev for this I think it would be wise to add some tests trying to connect to such illegal URLs but also some valid ones, with trainling "/" and without, with protocol spec and with just a hostname...
This is really a trouble for so many users, that we want to have some testing to ensure that we don't get a regression in future. And I think we should store the URL as full and valid URL in the account setting, so not what the user entered, that was autocorrected, but really what is used.
this one is closed, as we handle the non-standard port part in #100
If we for example omit the "http://" prefix the app terminates with something like:
=> we should catch the exception and show a message that an invalid URL was entered.