* [pve-devel] applied: [pbs-devel] [PATCH proxmox 0/3] s3 client: improve error logging for invalid requests
[not found] <20250723102601.495806-1-c.ebner@proxmox.com>
@ 2025-07-23 11:51 ` Thomas Lamprecht
0 siblings, 0 replies; only message in thread
From: Thomas Lamprecht @ 2025-07-23 11:51 UTC (permalink / raw)
To: pve-devel, pbs-devel, Christian Ebner
On Wed, 23 Jul 2025 12:25:58 +0200, Christian Ebner wrote:
> This patches improve error logging by refactoring the logging logic
> into a common helper and also covering responses with response status
> BAD_REQUEST. This has not been covered previously and helps to
> diagnose the reason for the bad request. In example, a malformed
> request might return the following response body:
>
> ```
> <?xml version="1.0" encoding="UTF-8"?>
> <Error>
> <Code>MalformedXML</Code>
> <Message>The XML you provided was not well formed or did not validate against our published schema.</Message>
> </Error>
> ```
>
> [...]
Applied, thanks!
[1/3] s3 client: fix minor whitespace issue
commit: 808b3725b63f82caf5fb49678593f7cf0aad1549
[2/3] s3 client: refactor error response body into dedicated helper
commit: d63fe256beb4c961ea1258cb114c12b2cc4a3b0e
[3/3] s3 client: log error response body for invalid request status codes
commit: 093dfeb8206aa3db405e27be92411794bcfc8780
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-07-23 11:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20250723102601.495806-1-c.ebner@proxmox.com>
2025-07-23 11:51 ` [pve-devel] applied: [pbs-devel] [PATCH proxmox 0/3] s3 client: improve error logging for invalid requests Thomas Lamprecht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox