Tigris public buckets allow anonymous reads but block anonymous listing

TL;DR

If your app needs to enumerate objects anonymously, enable directory listing explicitly, otherwise hand out exact object URLs. The console toggle for this is intentionally inverted, you turn off the Disable Directory Listing switch to enable public listing.

Steps

1. Do not assume a public bucket means a listable bucket. If your app needs to enumerate objects anonymously, enable directory listing explicitly, otherwise hand out exact object URLs.

When to use

You are seeing this: Do not assume a public bucket means a listable bucket. Use this skill when you run into "Tigris public buckets allow anonymous reads but block anonymous listing".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Making a Tigris bucket public allows anonymous reads of individual objects, but anonymous directory listing stays disabled by default. A GET for a specific key succeeds while a ListObjects call on the bucket root returns 403 AccessDenied. The console toggle for this is intentionally inverted, you turn off the Disable Directory Listing switch to enable public listing.

Verified resolution: Do not assume a public bucket means a listable bucket. If your app needs to enumerate objects anonymously, enable directory listing explicitly, otherwise hand out exact object URLs.

Source URL: https://github.com/tigrisdata/tigris-os-docs/blob/HEAD/docs/buckets/public-bucket.md