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
Creating a new TUS resource on WebDAV API with invalid names like " " sends a false response. It exits with 201 but the resource is not present for the requesting user.
Steps to reproduce
Steps to reproduce the behavior:
create user uu1
create a new TUS resource on the WebDAV API with these headers using the spaces WebDAV api
Upload-Length: 100
Upload-Metadata: filename <metadata>
Tus-Resumable: 1.0.0
Expected behavior
The HTTP status code should be 412
Actual behavior
The HTTP status code should is 201, but the file is also not found after the request.
kiranparajuli589
changed the title
upload file with invalid name succeeds with spaces DAV
TUS upload file with invalid name sends false response
Jan 28, 2022
Is this only a problem when using spaces or also without spaces? That is not clear to me reading the description and the example
kiranparajuli589
changed the title
TUS upload file with invalid name sends false response
using with spaces dav, TUS upload file with invalid name sends false response
Jan 31, 2022
Describe the bug
Creating a new TUS resource on WebDAV API with invalid names like
" "
sends afalse
response. It exits with201
but the resource is not present for the requesting user.Steps to reproduce
Steps to reproduce the behavior:
uu1
<metadata>
Expected behavior
The HTTP status code should be
412
Actual behavior
The HTTP status code should is
201
, but the file is also not found after the request.Then PROPFIND:
Setup
Please describe how you started the server and provide a list of relevant environment variables.
The text was updated successfully, but these errors were encountered: