Private bucket HEAD returns 403 for presigned download URL even when GET works

So far as I can tell this just started happening in the last few days. I use a Content-Length check to validate the size of file uploads and my service just recently started failing on private uploads.

We will take a look and get back to you. Could you share the bucket name by emailing us at help@tigrisdata.com

This behavior is expected and S3-compatible - it hasn’t changed recently. Pre-signed URLs are limited to the HTTP method they were generated for. So, a URL signed for GET cannot be used for HEAD, even though both target the same object.

In the Tigris Dashboard, you can generate pre-signed URLs for GET and PUT. If you need to perform a HEAD request, you can create a pre-signed URL using your access key and the AWS SDK (docs).

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.