Open benjaminguttmann-avtq opened 5 years ago
Hi,
we are currently using the fog-aliyun gem to store/get data from OSS. Unfortunately, it seems like the gem only supports internal endpoint URLs for the multipart upload part, as it is possible to provide the endpoint as an argument there (https://github.com/fog/fog-aliyun/blob/4513ff4f96aafbd8f6959057e16fbc330758c420/lib/fog/aliyun/requests/storage/put_object.rb#L114). For nearly all other calls the endpoint urls gets generated (e.g.: https://github.com/fog/fog-aliyun/blob/4513ff4f96aafbd8f6959057e16fbc330758c420/lib/fog/aliyun/requests/storage/head_object.rb#L16) which leads to the point that a non internal URL gets generated and used. This leads to timeouts if the VMs are not allowed to connect to the Internet.
Maybe the code could be adjusted to handle the endpoint generation like it is done in the multipart upload code.
Thanks for your help.
@dengqinsi : Any update on this topic?
Hi,
we are currently using the fog-aliyun gem to store/get data from OSS. Unfortunately, it seems like the gem only supports internal endpoint URLs for the multipart upload part, as it is possible to provide the endpoint as an argument there (https://github.com/fog/fog-aliyun/blob/4513ff4f96aafbd8f6959057e16fbc330758c420/lib/fog/aliyun/requests/storage/put_object.rb#L114). For nearly all other calls the endpoint urls gets generated (e.g.: https://github.com/fog/fog-aliyun/blob/4513ff4f96aafbd8f6959057e16fbc330758c420/lib/fog/aliyun/requests/storage/head_object.rb#L16) which leads to the point that a non internal URL gets generated and used. This leads to timeouts if the VMs are not allowed to connect to the Internet.
Maybe the code could be adjusted to handle the endpoint generation like it is done in the multipart upload code.
Thanks for your help.