# How to customize the URL reported back to the client in @tus/server

**URL:** <https://community.transloadit.com/t/how-to-customize-the-url-reported-back-to-the-client-in-tus-server/17457>\
**Category:** Tus\
**Created:** [February 6, 2025, 8:04am UTC](https://community.transloadit.com/t/how-to-customize-the-url-reported-back-to-the-client-in-tus-server/17457 "2025-02-06T08:04:20Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![marius](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.transloadit.com/marius/32/572_2.png) [@marius](https://community.transloadit.com/u/marius)\
**Post date:** [February 12, 2025, 9:07am UTC](https://community.transloadit.com/t/how-to-customize-the-url-reported-back-to-the-client-in-tus-server/17457/14 "2025-02-12T09:07:06Z")

</div>

> [@empz](#):
>
> Ok, but how exactly does the “single request to check if the server still has the file” works? Is there some event I can listen to?

Tus-js-client sends a HEAD request (see [Resumable upload protocol 1.0.x | tus.io](https://tus.io/protocols/resumable-upload)) to check the upload’s status. On the server-side, there are no events so far to modify the server’s response.

> [@empz](#):
>
> I’m simply trying to have a consistent response to the client in both cases: “new file uploaded” and “file was previously uploaded, returning existing URL”.

That’s currently not possible with tus-node-server. @Merlijn and I have been brainstorming about how this situation can be improved using metadata. The server could attach metadata once the upload is finished, which the client can then retrieve when either the upload is finished or the client notices that the upload is already done.

---

_[View the full topic](https://community.transloadit.com/t/how-to-customize-the-url-reported-back-to-the-client-in-tus-server/17457)._