:: beta7 :: wizard corrupts existing rest-server URI

[GuitarBilly]

:: INFO :: GUI: npbackup 3.1.0-beta7-windows-gui-x64-public-3.14-i 2026033101
W11 Enterprise 64bit

tried two scenarios which are both reproducible.

SCENARIO_A

1. convert existing config with simple rest-server connection, rest:http:// repo-URI and repo-password. rest:http://x300server:8888/NLNIJ01NB0507/npbackup.repo

2. start backup from commandline, everything runs perfectly.

3. open wizard, proceed to the second step "Select backup location"

4. notice that URI is mangled and Remote username and Remote password are filled in incorrectly [should be empty]

the new rest URI with (erased Remote username/password) becomes: rest:http://:@x300server:8888/NLNIJ01NB0507/

5. when saved the backup obviously fails because the repo URI is changed.
6. when I go to advanced config I can restore the rest-server URI and all is fine. p.s. there are no input fields in Advanced config to enter Remote username and Remote password??

SCENARIO_B

1. create new config and choose Advanced config. enter rest-sever URI rest:http://x300server:8888/NLNIJ01NB0507/npbackup.repo and a password. select one dummy file to back up. Accept the config.
2. repeat steps 2 to 6 from scenario_A

hereby I think I have excluded the config file migration process.

[deajan]

Thank you for that report.
I'm trying to strip the URI into pieces for the wizard, but obviously that's not an easy job, since there are optional parts (like username and password and port) which use the same separators for different parts.
I've yet to find a nice regex that can handle various forms like:

rest:http://x300server:8888/NLNIJ01NB0507/npbackup.repo
rest:http://x300server/NLNIJ01NB0507/npbackup.repo
rest:https://SOMEGUI:password@mobile.stash.mydomain.tld/somerepo
rest:https://SOMEGUI:password@mobile.stash.mydomain.tld:1234/somerepo

[deajan]

Bigger issue than I wanted it to be :(
Implementing a new parser in 2edb21b
This one allows auto_healing, eg it rips URI into pieces, tries to reconstruct it, and compares it to original in order to make sure parsing is done right.
I yet have to implement it in the wizard.

[GuitarBilly]

@deajan you could also keep it simple for now and make the wizard equal to the advanced config with only two fields; URI and repo password?
Then you can finish the parser later, i could also help with regex albeit my regex experience is on linux commandline and perl.

[deajan]

I would like to, but the wizard is a customer request ;)
Since that part is more tricky than I expected, I'll double check everything witb roundtip checks.

Anyway, I need to implement that fix ASAP, because I already got past my ETA, so my weekend is gonna be open-sourced lol.

Thanks for your offer though ;)