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
{{ message }}
This repository was archived by the owner on Jul 24, 2024. It is now read-only.
Please answer these questions before submitting your issue. Thanks!
What did you do?
Add a slash after S3's endpoint address when using BR backup.
E.g. http://xxxx:1234/
What did you expect to see?
No error or the error should be "the URL cannot end with a slash"
What did you see instead?
The error "msg:"Io(Custom { kind: Other, error: "failed to put object...)" appears.
After I delete this slash, BR works fine.
What version of BR and TiDB/TiKV/PD are you using?
v5.0.0-nightly
The text was updated successfully, but these errors were encountered:
gengliqi
changed the title
The extra slash after S3's endpoint address may lead to failure
The extra slash after S3's endpoint address may lead to error
Apr 7, 2021
gengliqi
changed the title
The extra slash after S3's endpoint address may lead to error
The extra slash after S3's endpoint address may lead to a strange error
Apr 7, 2021
In fact I'm not exactly sure this is a bug in minio or BR itself 😅. We can trim the final / but any chance some service requires that /?. Can we collect some behavior on non-minio services?
Please answer these questions before submitting your issue. Thanks!
What did you do?
Add a slash after S3's endpoint address when using BR backup.
E.g. http://xxxx:1234/
What did you expect to see?
No error or the error should be "the URL cannot end with a slash"
What did you see instead?
The error "msg:"Io(Custom { kind: Other, error: "failed to put object...)" appears.
After I delete this slash, BR works fine.
What version of BR and TiDB/TiKV/PD are you using?
v5.0.0-nightly
The text was updated successfully, but these errors were encountered: