REST: set error message extenesion for bad-request response log
We send it already to the user via the response body, but the log_response does not has, nor wants to have FWIW, access to the async body stream, so pass it through the ErrorMessageExtension mechanism like we do else where. Note that this is not only useful for PBS API proxy/daemon but also the REST server of the file-restore daemon running inside the restore VM, and it really is *very* helpful to debug things there.. Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
parent
835d0e5dd3
commit
f4d371d2d2
|
@ -254,7 +254,10 @@ impl tower_service::Service<Request<Body>> for ApiService {
|
|||
Some(apierr) => (apierr.message.clone(), apierr.code),
|
||||
_ => (err.to_string(), StatusCode::BAD_REQUEST),
|
||||
};
|
||||
Response::builder().status(code).body(err.into())?
|
||||
Response::builder()
|
||||
.status(code)
|
||||
.extension(ErrorMessageExtension(err.to_string()))
|
||||
.body(err.into())?
|
||||
}
|
||||
};
|
||||
let logger = config.get_file_log();
|
||||
|
|
Loading…
Reference in New Issue