Return 4xx errors from Hooks as 4xx errors. about tusd

[Acconut]

This change was made for various reasons when the entire hook system was overhauled for tusd v2. The new approach allows us to properly intingush between error responses that should be forwarded to the client and internal errors that indicate a failure while executing the hook. Furthermore, the new system provides a unified way of exchanging information between tusd and the hook implementation across the different hook systems (HTTP, file, gRPC etc).

In fact, the new hook system is much more powerful and allows you to completely control the response status, headers, and body by returning a corresponding hook response. Please consult https://tus.github.io/tusd/advanced-topics/hooks/#hook-requests-and-responses for more details. Does that not work for you?

[werfmark]

Thanks for the quick answer.

That makes sense, we were already expecting some sort of feature like this but glossed over this in the changes from version 1 to version 2 of the tusd server. We will take a look at this but at first glance seems to be much more powerful and versatile so should fit our purposes just fine.

[Acconut]

but glossed over this in the changes from version 1 to version 2 of the tusd server

We've all been there :) Glad it helped!