[Bug]: please send content-length header in http stream

[RBKreckel]

⚠️ 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

While discussing bug report 2037 for the Gnome Evince PDF viewer, it was discovered that GVFS supports seeking in DAV files if the server sends the content-length header in the http stream code
It seems like NextCloud doesn't send that header. Could it, please, send it?

Steps to reproduce

see above (bug description)

Expected behavior

see above (bug description)

Installation method

None

Nextcloud Server version

28

Operating system

Other

PHP engine version

PHP 8.2

Web server

Apache (supported)

Database engine version

MariaDB

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

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[SystemKeeper]

I assume your issue is not nextcloud, but apache. See https://bz.apache.org/bugzilla/show_bug.cgi?id=68973

[nbenitez]

But Apache is the only officially supported server for Nextcloud if I'm not mistaken, so at least the documentation for that should be updated to reflect this Apache bug or even better, add the mitigation for it (setting ap_trust_cgilike_cl).

[sorbaugh]

Discussing with @icewind1991 it looks like enabling this in the .htaccess would be the simplest way to achieve this.