Incorrect Backblaze B2 suffix in S3 PROVIDERS list

[metadaddy]

Hi there - it looks like there’s a bug in the S3 Extension. The PROVIDERS list in org.lucee.extension.resource.s3.S3 contains an entry ".backblaze.com", but Backblaze B2 S3-compatible API endpoints have a ".backblazeb2.com" suffix.

From my reading of the code, it’s possible to workaround this by setting the desired endpoint as the lucee.s3.host / LUCEE_S3_HOST system property / environment variable, but it should be fixed so that paths of the form s3://my-application-key-id:my-application-key:us-west-004@s3.us-west-004.backblazeb2.com/my-bucket/images/my-file.png work correctly.

I just created an account over at https://luceeserver.atlassian.net/ - shall I create an LDEV issue there?

[Zackster]

please file a ticket, even a PR if you feel like it!

If you are interested in providing us with a test account, we can add backblaze to our github actions too?

For context

Blackblaze B2 Bucket support

Hi there - I run evangelism at Backblaze; part of my role is to handle questions just like this. I didn’t notice this one earlier, since my Google alert is for backblaze, with only one l I’m guessing this is the same question I just answered over in our subreddit - it seems like there’s a bug in the S3 extension - it has an incorrect domain name suffix for Backblaze B2. I gave a workaround on the Reddit post, and posted a topic here explaining the bug before I saw this one.

[Zackster]

bug filed [LDEV-4591] - Lucee

[metadaddy]

bug filed [LDEV-4591] - Lucee

PR looks good to me!

Thanks, @Zackster - I would have done this myself, but I went out on vacation soon after sending that message

If you are interested in providing us with a test account, we can add backblaze to our github actions too?

Anyone can create a Backblaze B2 account and get 10 GB storage free forever. If you need more than that, I can create a bucket in an internal account and give you credentials.