[BUG] custom server URL validation fails on URLs lacking TLD

[smartin015]

Describe the bug

There is a regression from previous TSD behavior where I was successfully able to configure a connection to my self-hosted Obico server with http://hostname:3334.

To Reproduce

1. Go to octoprint instance, with fresh installation of Obico plugin
2. Click "Custom server" radio button, type e.g. http://hostname:3334/, click Continue

Rather than continuing to the next screen, an Invalid server address error appears and the wizard cannot continue.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Linux
• Browser: Chrome
• Version: 102.0.5005.75

Additional context

The regex you're using for URL validation requires that there's a TLD after the hostname. While this is technically correct, the TLD can be left implicit when resolving hostnames on a local network. A host named host1 for instance, can be resolved with http://host1:3334, although it may sometimes be implicitly routed as e.g. http://host1.local:3334 (I'm a bit fuzzy on this - appending .local appears to work here, but IIRC windows prefers .lan... and users can set their own local network TLD. Confusing).

I recommend changing your regex to:

^https?:\/\/(www\.)?[-a-zA-Z0-9@:%._\+~#=]{1,256}\b([-a-zA-Z0-9()@:%_\+.~#?&//=]*)$

Which is more permissive and lacks the TLD constraint, bringing the process back to parity with pre-Obico.

[kennethjiang]

Good point. Feel free to send a PR for it and I'll merge it.