doc: Polish changelogs

This commit is contained in:
Leo R. Lundgren 2023-04-23 22:27:27 +02:00
parent 253bebb096
commit 94d5861c50
4 changed files with 15 additions and 15 deletions

View file

@ -1,4 +1,4 @@
Enhancement: Cache basic auth credentials
Enhancement: Cache basic authentication credentials
To speed up the verification of basic auth credentials, rest-server now caches
passwords for a minute in memory. That way the expensive verification of basic

View file

@ -1,8 +1,8 @@
Bugfix: Allow usernames containing underscore
Bugfix: Allow usernames containing underscore and more
The security fix in rest-server 0.11.0 (#131) disallowed usernames containing
and underscore "_". We have changed the list of allowed characters to now include
unicode characters, numbers, "_", "-", "." and "@".
and underscore "_". The list of allowed characters has now been changed to
include Unicode characters, numbers, "_", "-", "." and "@".
https://github.com/restic/restic/issues/183
https://github.com/restic/restic/pull/184

View file

@ -1,7 +1,7 @@
Enhancement: Allow configurable location for .htpasswd file
Enhancement: Allow configurable location for `.htpasswd` file
It is now possible to change the location of the .htpasswd file using the
--htpasswd-file option.
It is now possible to specify the location of the `.htpasswd`
file using the `--htpasswd-file` option.
https://github.com/restic/restic/issues/187
https://github.com/restic/restic/pull/188

View file

@ -1,13 +1,13 @@
Bugfix: Return "internal server error" if files cannot be read
Bugfix: Return 500 "Internal server error" if files cannot be read
When files in a repository cannot be read by rest-server, for example after
running `restic prune` directly on the server hosting the repositories, then
rest-server returned "Not Found" as status code. This is extremely confusing
for users.
running `restic prune` directly on the server hosting the repositories in a
way that causes filesystem permissions to be wrong, rest-server previously
returned 404 "Not Found" as status code. This was causing confusing for users.
The error handling has been fixed to only return "Not Found" if the file
actually does not exist. Otherwise an internal server error is reported to the
user and the underlying error is logged at the server side.
The error handling has now been fixed to only return 404 "Not Found" if the
file actually does not exist. Otherwise a 500 "Internal server error" is
reported to the client and the underlying error is logged at the server side.
https://github.com/restic/restic/issues/1871
https://github.com/restic/rest-server/pull/194
https://github.com/restic/rest-server/pull/195