feat: new option customEndpointHost #1358
Conversation
|
@peerless-hero - thank you . We comply with AWS S3 both path style and DNS Style. Which provider is this ? Please elaborate with details and also please add functional tests if it is compatible with AWS S3. |
I am using Alibaba Cloud's OSS storage, which features a domain name style of <bucketName>.oss-<regionId>.aliyuncs.com. Additionally, it provides S3-compatible APIs, allowing me to use the minio SDK seamlessly. When initializing with the minio SDK, setting the endpoint to oss-<regionId>.aliyuncs.com enables normal usage. Due to business requirements, I now need to bind a personalized domain name, such as oss.mydomain.com. According to their documentation, the binding method involves adding a CNAME record for mydomain.com and pointing it to <bucketName>.oss-<regionId>.aliyuncs.com . At this point, if I set the endpoint to oss.mydomain.com and attempt to concatenate <bucketName> to form <bucketName>.oss.mydomain.com, it is not functional. Many cloud providers offer documentation on binding custom domain names. For reference, here are some links: Binding custom domain names is not an uncommon scenario, so I hope this PR can make the minio SDK more flexible in supporting custom domain names. |
Some cloud storage providers support custom domain names, but the existing configuration automatically appends the bucket name, causing service access issues.
For instance, the intended access should be to
oss.example.com, but it instead becomesbucket.oss.example.com, resulting in the service being unreachable.To address this situation, this Pull Request (PR) introduces the
customEndpointHostconfiguration. When enabled, it uses the endpoint as the final request hostname without processing additional strings, allowing the aforementioned example to function correctly.