env variables do not work properly (restic_rest_username, restic_rest_password)

[abcnorio]

Output of rest-server --version

rest-server version rest-server 0.14.0-dev compiled with go1.23.5 on linux/amd64

restic on Debian trixie:

restic 0.14.0-1+b5

Problem description / Steps to reproduce

rest server call

/usr/local/bin/rest-server --path /home/restic/REPO/ --tls --tls-cert /home/restic/REPO/restserver_public.key --tls-key /home/restic/REPO/restserver_private.key --append-only --htpasswd-file /home/restic/REPO/.htpasswd --private-repos --log -

Export on a different computer (client, Debian trixie) of

export RESTIC_REST_USERNAME=$restuser
export RESTIC_REST_PASSWORD=$restuserpwd

along with

export RESTIC_REPOSITORY="rest:https://$resticIP:8000/$localname.$backuptype"

does not work but

export RESTIC_REPOSITORY="rest:https://$restuser:$restuserpwd@$resticIP:8000/$localname.$backuptype"

works.

The error on the restic client is

Fatal: unable to open config file: unexpected HTTP response (401): 401 Unauthorized

and on the rest server

"HEAD /$localname.$backuptype/config HTTP/2.0" 401 13 "" "Go-http-client/2.0"

Using the --no-auth option works or switching to the different restic_repository export call above. Thus, basically it works but not with the env variables set.

Expected behavior

Export of the two variables above should work.

Actual behavior

Export of the two variables above does not work but to specify them in the repository export call works.

Do you have any idea what may have caused this?

nope.
But the behavior is reliable as outlined above.

Did rest-server help you today? Did it make you happy in any way?

rest-server is pretty cool, esp. along with the systemd service and the cap/ restrictions outlined. Great work!