Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

The extra slash after S3's endpoint address may lead to a strange error #992

Open
gengliqi opened this issue Apr 7, 2021 · 2 comments
Open
Labels
severity/moderate type/bug Something isn't working

Comments

@gengliqi
Copy link

gengliqi commented Apr 7, 2021

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    Add a slash after S3's endpoint address when using BR backup.
    E.g. http://xxxx:1234/

  2. What did you expect to see?
    No error or the error should be "the URL cannot end with a slash"

  3. 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.

  4. What version of BR and TiDB/TiKV/PD are you using?
    v5.0.0-nightly

@gengliqi gengliqi added the type/bug Something isn't working label Apr 7, 2021
@gengliqi 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 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
@kennytm
Copy link
Collaborator

kennytm commented 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?

@kennytm
Copy link
Collaborator

kennytm commented Jun 1, 2021

as shown in #1162, also affects Hitachi Content Platform (HCP).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity/moderate type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants