410 on Head request from TUS client (uppy) to resumable endpoint

[logemann]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When using uppy and tus for making resumable upload work via the supabase endpoint, i get a 410 on a HEAD request, but the upload itself works anyway.

The supabase endpoint is: http://127.0.0.1:54321/storage/v1/upload/resumable

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

I basically used https://github.com/supabase/supabase/tree/master/examples/storage/resumable-upload-uppy as a blueprint but with these changes:

• no HTML embed but NextJS component usage of <Dashboard>
• supplying a user JWT instead of ANON key
• applied "authenticated" RLS to bucket to match with the user JWT

Note: I ve tested only in local dev mode with "supabase start".

Expected behavior

No errors on client side while doing all those XHR calls.

Screenshots

System information

• OS: MacOS
• Browser: chrome
• Version of supabase-js: 2.39.0
• Version of CLI: 1.123.4
• Version of Node.js: 20.10.0

[fenos]

That is expected because the URL you are trying to upload to is expired.

By default an upload URL is valid for up to 24h after that you'll receive 410 Gone.
The TUS js client will create a new upload URL and automatically start the upload.

Let me know if this makes sense or if you have any other questions.
Closing for now