Enhancement: Add event to allow dynamic custom request info per Tus part(chunk)

[yoavniran]

Discussed in #906

^{Originally posted by joel-s October 2, 2025}
I'm using TusUploady with a drop zone to send files.

About half or a third of the time, TusUploady stops sending the metadata from my useRequestPreSend hook. It always sends all the metadata for the first file, but after one or two files it stops sending the useRequestPreSend metadata and only sends the metadata passed to UploadDropZone. This causes uploads to fail because the server can't read the names of files.

Any ideas what might be causing this? I'm open to debugging suggestions. I can't post the whole source code, but here are some relevant parts:

        <TusUploady
            destination={{
                url: `${import.meta.env.VITE_BACKEND_URL}/v1/uploads`,
                headers: {
                    Authorization: `Bearer ${accessToken}`,
                },
            }}
            resumeHeaders={{
                // Include the Authorization header for resume requests (HEAD)
                Authorization: `Bearer ${accessToken}`,
            }}
            autoUpload
            forgetOnSuccess
            sendDataOnCreate
        >

const DropZone: React.FC<DropZoneProps> = ({ basePath, className, children }: DropZoneProps) => {
    useRequestPreSend(({ items }) => {
        const name = items[0]?.file.name;

        return {
            options: {
                params: {
                    filename: name,
                },
            },
        };
    });

    return (
        <UploadDropZone
            id="upload-drop-zone"
            className={twMerge(
                "tw:flex tw:h-full tw:w-full tw:flex-col tw:justify-between tw:p-3",
                className,
                styles.dropZone,
            )}
            onDragOverClassName={styles.dragOver}
            htmlDirContentParams={{ recursive: true, withFullPath: true }}
            params={{ base_path: basePath }}
        >

I checked if useRequestPreSend was ever invoked with 0 items or a missing filename, and the answer is no. I think it's not getting called at all in the failure cases.

[joel-s]

Hi @yoavniran, how's the debugging going? We're hoping to get some software that uses Uploady and Tus working within the next couple weeks. Anything you could use my help with?

[yoavniran]

Hey @joel-s
Thanks for the offer, I've been in the middle of investigating the issue and I believe I've found insights. Some are hopeful, some may take more work to fix/circumvent.
This is happening while I've been in the middle of moving (myself, family + 1 cat) to a different country and settling in so handling times may vary 😅

I will need a bit more time to conclude everything and implement what fixes are possible quickly.

One thing I'm not sure if that was clear enough about how to apply headers dynamically (useRequestPreSend) is that the headers object is nested in the destination object.

useRequestPreSend(({ items }) => {
        const name = items[0]?.file.name;

        return {
            options: {
               destination: {
                  headers: {
                     Authorization: "bearer..."
                  } 
               }
            },
        };
    });

That as far as I can tell will allow you to set the header per file being uploaded.

As for setting headers/params per chunk, that will require some work as the Tus Sender is already using the useChunkStartListener handler. Unfortunately, I haven't had time yet to dive deeper than that.

As things are settling at home, I'm hopeful I can finalize and release over the coming week.

[joel-s]

Thank you for the update and the guidance. Your guidance helped a lot, since it means we're using more recent tokens. Since I made this change, I haven't run into any Uploady failures. (I used to run into 401 failures a lot.)

I hope your move has gone well, and again, thank you for the tip.

Our customers may get failures if they upload large files that take more than 5 minutes to transfer... so if you have a way to update tokens even more frequently, that will be great.

[joel-s]

Let me know if there's something I can help with such as code review or trying out some changes.

[joel-s]

Should we change the title of this issue to something like "Let TUS Uploady users update tokens per chunk, so long uploads don't fail with 401 errors"? I think this is the one Uploady feature still missing.

[yoavniran]

Hey @joel-s
Happy to hear that the info here helped.
The move indeed went well, tiring and busy, but so far so good. Thanks!

I'll change the issue since indeed its not really a bug (as it turns out) and work here on an enhancement to add a new Tus Sender event for adding dynamic info per chunk/part

[yoavniran]

Hey @joel-s
It took a while, but I've finally managed to work on the enhancement to allow dynamically setting headers on a Tus part(chunk) request before it starts.

I published the new feature in release candidate 1.12.0-rc.0

You can see the details and example of the new event handler hook: here.

It would be great if you could check and validate before I release it as the next Uploady version.

Thanks!