[Bug]: dav search request responds with HTTP/1.1 500 Internal Server Error

[wlklch]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

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

1. see above

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?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

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.

[SystemKeeper]

Wondering if this is also related to #49960 maybe?

[wlklch]

• I do not understand what to Revert: Restore dav error response #49960 wants to do and why. If you have a (link to) an explanation, I will look into it
• on nextcloud 20 it works correctly ...