# \`response\` is always empty

**URL:** <https://community.transloadit.com/t/response-is-always-empty/16485>\
**Category:** Uppy\
**Created:** [February 21, 2023, 8:11am UTC](https://community.transloadit.com/t/response-is-always-empty/16485 "2023-02-21T08:11:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sneko](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.transloadit.com/sneko/32/786_2.png) [@sneko](https://community.transloadit.com/u/sneko)\
**Post date:** [February 21, 2023, 8:11am UTC](https://community.transloadit.com/t/response-is-always-empty/16485/1 "2023-02-21T08:11:26Z")

</div>

Hi,

I’m using Uppy with React.js and when my `tus` server returns a 401 error for example, it does trigger the `upload-error` but the `response` parameter is always undefined (whereas in my browser network section I can see the error).

If I look into the `file` parameter there in nothing. Only the `error` has some information about 401 but it’s all stringified so it’s complicated to do regexp on this… it would make no sense.

I searched a lot but didn’t find someone in the same case. Any idea what could cause this? My component managing Uppy looks like: [mediature/Uploader.tsx at dev · inclusion-numerique/mediature · GitHub](https://github.com/inclusion-numerique/mediature/blob/dev/apps/main/src/components/uploader/Uploader.tsx)

Thank you,

* * *

It’s maybe related to my other issue… [Having a `500` code error triggers the `upload-success` event · Issue #4324 · transloadit/uppy · GitHub](https://github.com/transloadit/uppy/issues/4324) looks like response are not passed from tus client to Uppy… any idea?