You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our server endpoint returns 201 HTTP status code, but filedrop.js considers this as an error and calls the error handler. Given the semantics, this should be considered success and call the file.event("done", ...) listener.
The text was updated successfully, but these errors were encountered:
Hi @ProgerXP, @bollwyvl, according to this commit, it seems intentional but I couldn't find any reason why should 2xx responses be considered failures. What was your use case?
Our server endpoint returns 201 HTTP status code, but filedrop.js considers this as an error and calls the error handler. Given the semantics, this should be considered success and call the file.event("done", ...) listener.
The text was updated successfully, but these errors were encountered: