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
Its more of a suggestion than any issue/improvement.
Handling HTTP Redirect error is an important feature and widely used.
We clearly understand the intention to remove redirect handling support completely - minio/minio#13918.
Although, it fixed the issue faced during AWS S3 resource access across regions.
Minio Client SDK is being widely used for other Object Store vendors as well, which is not completely dependent on Regions.
My suggestion here is, why cant we make Redirection Handling as an optional configurable feature in minio-go (Setting Disabled by Default), so that whoever wants to make use of redirection they can continue using that feature without any hassle.
Redirection support is not part of S3 API and is out of scope for this SDK. Let me know if this supported in AWS SDK if yes we can bring it back otherwise sorry.
My suggestion here is, why cant we make Redirection Handling as an optional configurable feature in minio-go (Setting Disabled by Default), so that whoever wants to make use of redirection they can continue using that feature without any hassle.
We don't want to carry code that no one uses and will never use it properly.
Its more of a suggestion than any issue/improvement.
Handling HTTP Redirect error is an important feature and widely used.
We clearly understand the intention to remove redirect handling support completely - minio/minio#13918.
Although, it fixed the issue faced during AWS S3 resource access across regions.
Minio Client SDK is being widely used for other Object Store vendors as well, which is not completely dependent on Regions.
My suggestion here is, why cant we make Redirection Handling as an optional configurable feature in minio-go (Setting Disabled by Default), so that whoever wants to make use of redirection they can continue using that feature without any hassle.
So, the changes needed would be simple
The text was updated successfully, but these errors were encountered: