Skip to content

fix(s3): omit empty x-amz-tagging header for B2 compatibility #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ynsta merged 1 commit into from
May 20, 2026
Merged

fix(s3): omit empty x-amz-tagging header for B2 compatibility #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion s3proxy/internal/s3/s3.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,11 +226,15 @@ func (c Client) PutObject(ctx context.Context, bucket, key, tags, contentType, o
Bucket: &bucket,
Key: &key,
Body: bytes.NewReader(body),
Tagging: &tags,
Metadata: metadata,
ContentType: &contentType,
ObjectLockLegalHoldStatus: types.ObjectLockLegalHoldStatus(objectLockLegalHoldStatus),
}
// Only forward Tagging when the client supplied a non-empty value. Some S3-compatible
// backends (e.g. Backblaze B2) reject any presence of x-amz-tagging, even when empty.
if tags != "" {
putObjectInput.Tagging = &tags
}
if sseCustomerAlgorithm != "" {
putObjectInput.SSECustomerAlgorithm = &sseCustomerAlgorithm
}
Expand Down
Loading