[Bug]: dav search request responds with HTTP/1.1 500 Internal Server Error #49972
Labels
Comments
wlklch
added
0. Needs triage
|
Wondering if this is also related to #49960 maybe? |
|
susnux
added a commit
that referenced
this issue
Mar 19, 2025
* Resolves #49972 Currently a TypeError is thrown when casting fails, this lead to a HTTP 500 error. Instead throw a proper InvalidArgumentError so the user receives a HTTP 400. Signed-off-by: Ferdinand Thiessen <[email protected]>
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
a SEARCH request to .../remote.php/dav/uri ... for a bad fileid gives in consistent reponses:
<d:searchrequest xmlns: ......
<d:where>
<d:eq><d:prop>oc:fileid/</d:prop><d:literal>q234</d:literal></d:eq>
responds with HTTP/1.1 500 Internal Server Error and I could not find any indication in the response header, that it is simply bad input data
searching for fileid=234q or fileid=234, however, both correctly respondswith HTTP/1.1 207 Multi-Status and the body an empty xml-element <d:multistatus .../>
Steps to reproduce
Expected behavior
multistatuis as described above
Nextcloud Server version
30
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
the server is my hosting provider, so I do not know any details, to provide them needs some work. However I guess, the details are irrelevant.
The text was updated successfully, but these errors were encountered: