Fabrizio

Hi @joeldomke, This is an interesting scenario, conceptually objects are immutable. This is also the case in S3. In S3 you cannot rename an object, you'll instead need to copy...

Hi, this is now fixed, and we do not change the id of a moved object

Hello Guys! This PR will be merged very soon! I was very busy with some clean-ups on other parts of the code base! Stay tuned!

@imageck thanks for this, we'll amend the status code!

This is now being fixed

Returning 400 instead of 404 was a legacy decision to force the user to branch error handling with the response code. It is arguably not semantically correct as you mentioned....

I believe that the range header is not supported on the File System Storage just yet. The S3 Backend adapter should support it Open for contributions on this

This is now fixed by https://github.com/supabase/storage/pull/358

It's on the work

We already have a backend method to check the existence of an object, simply using a HEAD request instead of a GET on a specific object will return empty content...