Recently users have reported that assets hosted on Tigris have been blocked by several ISPs due to reports of malicious content on the Tigris subdomain. We’ve been working with security vendors to get removed from these blocklists. However, the long term solution that prevents this from happening again is to make it so that the Tigris subdomain is no longer the common denominator in identifying content.
In order to make unique subdomains per bucket, we’re moving to virtual host style URLs as the default. Path name style URLs will still work for buckets created before today, but all new buckets will require a virtual host style URL. If you try to use a path name style URL with a newly created bucket, you’ll get a 403 error.
The path style URL looks like this: https://fly.storage.tigris.dev/tigris-example/bar.txt
The virtual host style URL looks like this: https://tigris-example.fly.storage.tigris.dev/bar.txt
For newly created buckets, you’ll need to configure your SDK to use virtual host style URLs. We’ve shared example code here for our most commonly used frameworks: Moving to Virtual Hosted URLs | Tigris Object Storage
You’ll also need to update your pre-signed URL code for newly created buckets. We updated our example code here: Presigned URLs | Tigris Object Storage Documentation
We apologize for the breaking change, and we want to help folks transition smoothly. Please ask for help on this thread if you run into any issues.