AdityaandNick Craig-Wood
ea589de941
Ceph RGW (and Linode Object Storage, which is Ceph-backed) can break SigV4 when Accept-Encoding is included in the signature, especially when a reverse proxy rewrites that header. GCS already sets this quirk; apply the same default for Ceph and Linode as suggested in #8206.
26 lines
650 B
YAML
26 lines
650 B
YAML
name: Ceph
|
|
description: Ceph Object Storage
|
|
region: {}
|
|
endpoint: {}
|
|
location_constraint: {}
|
|
acl: {}
|
|
server_side_encryption:
|
|
'': None
|
|
AES256: AES256
|
|
aws:kms: aws:kms
|
|
bucket_acl: true
|
|
sse_customer_algorithm: true
|
|
sse_customer_key: true
|
|
sse_customer_key_base64: true
|
|
sse_customer_key_md5: true
|
|
sse_kms_key_id: true
|
|
quirks:
|
|
list_version: 1
|
|
force_path_style: true
|
|
list_url_encode: false
|
|
use_already_exists: false
|
|
# Ceph RGW (and reverse proxies such as Cloudflare in front of it) can
|
|
# mutate Accept-Encoding and break SigV4 when that header is signed.
|
|
# See: https://github.com/rclone/rclone/issues/8206
|
|
sign_accept_encoding: false
|