Chris Lu 3d4bef39dd fix(replication/s3sink): forward entry.Attributes.Mime as ContentType ...

Same gap as the remote_storage S3 client: filer.replicate uploads via
s3manager.Uploader without populating ContentType, so replicated objects
on S3-compatible backends (e.g. Backblaze B2) store binary/octet-stream
and browsers refuse to render HTML, CSS, etc.

Pass entry.Attributes.Mime through to UploadInput.ContentType, leaving
the header unset when no Mime is recorded so the remote keeps its own
default.

2026-05-27 11:14:14 -07:00

..

repl_util

go fmt

2026-04-10 17:31:14 -07:00

sink

fix(replication/s3sink): forward entry.Attributes.Mime as ContentType

2026-05-27 11:14:14 -07:00

source

fix(sync): use per-cluster TLS for HTTP volume connections in filer.sync (#8974)

2026-04-07 14:11:44 -07:00

sub

notification.kafka: add SASL authentication and TLS support (#8832)

2026-03-29 13:45:54 -07:00

replicator_test.go

Adjust rename events metadata format (#8854)

2026-03-30 18:25:11 -07:00

replicator.go

fix: replication sinks upload ciphertext for SSE-encrypted objects (#8931)

2026-04-06 00:32:27 -07:00