v.20.11Improvement

Workaround for S3 URL Handling with Nginx Proxy

Official CH changelog text
Workaround for use S3 with nginx server as proxy. Nginx currenty does not accept urls with empty path like http://domain.com?delete, but vanilla aws-sdk-cpp produces this kind of urls. This commit uses patched aws-sdk-cpp version, which makes urls with "/" as path in this cases, like http://domain.com/?delete. #16814 (ianton-ru).
Workaround for using S3 with nginx proxy servers by ensuring URLs have a non-empty path. This update patches the AWS SDK to generate URLs with a "/" path (e.g., http://domain.com/?delete) instead of empty paths (e.g., http://domain.com?delete) to be compatible with nginx.

Why it matters

Nginx does not accept URLs with empty paths, which causes issues when ClickHouse uses S3 storage through an nginx proxy, because the vanilla AWS SDK generates such URLs. This feature fixes URL formatting to ensure compatibility and proper operation of the S3 storage backend behind nginx proxies.

How to use it

This fix is applied internally by using a patched version of the AWS SDK. Users do not need to perform additional configuration to enable this behavior; it is applied automatically when using S3 with an nginx proxy.

Related resources

PreviousNext