Closed taran-p closed 10 months ago
This needs to be also on the server side @taran-p client
side you don't have much context. Some times certain endpoints might return 200 OK. You should be able to perform "MinIO" only checks to make sure this is a MinIO-only server for that it needs to be done via an authenticated endpoint.
What happens if you this command is executed against AWS S3 ? no error at all ?
@harshavardhana do you mean I need to add an authenticated endpoint for this or does it already exist?
When I tested on S3 and GCS it errored properly.
@harshavardhana do you mean I need to add an authenticated endpoint for this or does it already exist?
It would be best if you let the MinIO server decide this where we can do specific API checks. Anyone can fake this endpoint if its purely on mc
to decide.
We do not have to do a heuristical approach, we can be precise. For that, you need to let this information be sent to MinIO and then MinIO validates whether it that it's the right endpoint.
Community Contribution License
All community contributions in this pull request are licensed to the project maintainers under the terms of the [Apache 2 license] (https://www.apache.org/licenses/LICENSE-2.0). By creating this pull request I represent that I have the right to license the contributions to the project maintainers under the Apache 2 license.
Description
Verifies that the target server for a bucket replication command is MinIO
Motivation and Context
It is currently possible to replicate buckets to non-MinIO hosts, which can lead to unexpected behavior
How to test this PR?
Attempt to replicate to MinIO and non-MinIO servers.
Types of changes
Checklist:
commit-id
orPR #
here)