SignatureDoesNotMatch when port is 80

I’ve discovered an issue with using the minio dotnet client when connected to a minio server over port 80. The signature generated by the client sets host header using the following code: SetHostHeader(request, client.BaseUrl.Host + ":" + client.BaseUrl.Port); This is V4Authenicator.cs: line 114 The issue is, the server doesn’t seem to include the port number with host resulting in a signature mismatch.

I’ve verify buy running the dot-net samples code and removing port number from SetHostHeader. The signature mismatch issue goes away.

[Maximkaaa]

@poornas I’ve faced the same issue, but connecting to a different s3 server. For my work I need to use Yandex S3, which works great with official Java tools and python boto. But MinIO client failes to authenticated with it for this reason. It seems that the server implementation does not expect default :80 port to be present in the host header.

In my case it seems to be a bug in the server implementation. Still other tools work fine with it since they do not include the :80 port in the host header. Do you think it can be beneficial to also not include default port, as more popular tools do, to provide better support for different S3 server implementations? If so, I can make a PR.

[sergei66666]

@Maximkaaa Just to note: yandex team fixed it, now it works fine.