Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Incorrect Backblaze B2 suffix in S3 PROVIDERS list

Description

Hi there - it looks like there’s a bug in the S3 Extension. The PROVIDERS list 1 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.

Environment

None

Activity

Show:

Zac Spitzer 15 August 2023 at 08:29

confirmed this is working, however, there is a new issue

Michael Offner 7 August 2023 at 14:29

Zac Spitzer 29 June 2023 at 11:45

[java] [script] Service [ s3_backblaze ] is [ s3 custom Connection verified ]

but then we get

Zac Spitzer 29 June 2023 at 11:21
Edited

requires the following env vars to be enabled

Zac Spitzer 28 June 2023 at 10:13

Fixed

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Parent

Sprint

Created 28 June 2023 at 10:10
Updated 15 August 2023 at 08:29
Resolved 15 August 2023 at 08:29