You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am encountering an issue with AWS URL formatting when using the minio-cpp client. Following the BucketExists example provided in the documentation, an error is raised regarding host resolution.
When client.Debug(true); is enabled, the following output is observed:
* Could not resolve host: sa-soundnodes.eu-central-1.amazonaws.comeu-central-1.amazonaws.com
* Closing connection 0
unable to do bucket existence check; server failed with HTTP status code 0
It seems that the AWS URL is not formatted correctly, leading to a concatenated host name that cannot be resolved (sa-soundnodes.eu-central-1.amazonaws.comeu-central-1.amazonaws.com).
Expected Behavior
The client should properly format the AWS URL so that the host resolves correctly.
Comparison with Python Client
I do not have this issue when using the Python client for MinIO. The following Python code works correctly without any host resolution problems:
Description:
Hello,
I am encountering an issue with AWS URL formatting when using the
minio-cpp
client. Following theBucketExists
example provided in the documentation, an error is raised regarding host resolution.Code to reproduce the issue
Debugging Output
When
client.Debug(true);
is enabled, the following output is observed:It seems that the AWS URL is not formatted correctly, leading to a concatenated host name that cannot be resolved (
sa-soundnodes.eu-central-1.amazonaws.comeu-central-1.amazonaws.com
).Expected Behavior
The client should properly format the AWS URL so that the host resolves correctly.
Comparison with Python Client
I do not have this issue when using the Python client for MinIO. The following Python code works correctly without any host resolution problems:
The Python client successfully checks the existence of the bucket without any issues.
Environment
minio-cpp
version: 0.3.0The text was updated successfully, but these errors were encountered: