-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix S3 ObjectStore proxy option #26463
Conversation
Signed-off-by: Maxime Besson <maxime.besson@worteks.com>
Signed-off-by: Maxime Besson <maxime.besson@worteks.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't test but it looks sane
Signed-off-by: Maxime Besson <maxime.besson@worteks.com>
Sorry for the delay in fixing this, I did not realize the comment on getProxy() was a blocker. Any chance this PR could get in NC22? |
Failures unrelated |
Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 |
/backport to stable22 |
Hello @juliushaertl |
Thanks for the hint, seems the backport bot was not picking that up. Let me retry. |
/backport to stable22 |
The
proxy
option in S3 object store does not current worktries to set an unknown/deprecated "request.options" key when constructing a S3Client. The correct one is "http"
Additionally, S3ObjectTrait::readObject uses fopen() directly, so object store proxy options must also be passed to it