superseded: [PATCH proxmox] s3-client: copy_object: always set Content-Type header

[Hannes Laimer <h.laimer@proxmox.com>]

superseded-by:
https://lore.proxmox.com/pbs-devel/20260316141940.3576-1-h.laimer@proxmox.com/T/#u

On 2026-03-11 10:56, Hannes Laimer wrote:
> Some S3 providers drop all source metadata, including Content-Type,
> when using x-amz-metadata-directive REPLACE unless it is explicitly
> provided in the copy request. This caused s3_refresh to fail with
> "missing header 'content-type'" on such providers when fetching
> objects moved via copy_object.
> 
> Setting Content-Type explicitly is a no-op for providers that already
> preserve it, so this is safe regardless of the provider.
> 
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
> did notice this with RustFS, MinIO did not have that problem
> 
>  proxmox-s3-client/src/client.rs | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/proxmox-s3-client/src/client.rs b/proxmox-s3-client/src/client.rs
> index 81645716..baa8345e 100644
> --- a/proxmox-s3-client/src/client.rs
> +++ b/proxmox-s3-client/src/client.rs
> @@ -602,6 +602,7 @@ impl S3Client {
>              .method(Method::PUT)
>              .uri(self.build_uri(&destination_key, &[])?)
>              .header("x-amz-copy-source", HeaderValue::from_str(&copy_source)?)
> +            .header(header::CONTENT_TYPE, "binary/octet-stream")
>              .header(
>                  "x-amz-metadata-directive",
>                  HeaderValue::from_str("REPLACE")?,