Open gonzalo opened 1 week ago
Cc @szaimen
cc @artonge
Makes sense. Good catch! Up to submitting as a PR? I wonder if there's any real difference between adjusting the regexp versus using SetEnvIfNoCase
?
Interesting never heard about it but it seems exactly for that
The SetEnvIfNoCase is semantically identical to the SetEnvIf directive, and differs only in that the regular expression matching is performed in a case-insensitive manner. For example:
SetEnvIfNoCase Host Example\.Org site=example
This will cause the site environment variable to be set to "example" if the HTTP request header field Host: was included and contained Example.Org, example.org, or any other combination.
Will try it tomorrow morning and confirm it to you. Cleaner is better!
Just tested on my test and prd environments SetEnvIfNoCase does the same stuff, so I suggest to use in .htaccess (currently in my vhost file, to avoid been overridden by an update).
<IfModule mod_setenvif.c>
SetEnvIfNoCase Transfer-Encoding "chunked" proxy-sendcl=1
</IfModule>
⚠️ This issue respects the following points: ⚠️
Bug description
There are know problems with MacOS+WebDav+Apache+php-fpm https://docs.nextcloud.com/server/latest/user_manual/en/files/access_webdav.html#accessing-files-using-macos
If you use MacOS finder client to connect via WebDavto your nextcloud instance and php-fpm running, you will soon find that transfer crashes, giving you a -36 error. This comes from a problem with Content-Length sent to backend.
For dealing with this .htaccess file has this code
However this doesn't work with Macos Webdav Darwin client beacuse the header has a capital letter -> "Chunked" (checked by logs) So you can fix it making condition case insensitive
NOTE: apache will upload the file to their tmp folder before passing it to php. Take care of this in case you have restrictions on that folder.
Steps to reproduce
Expected behavior
To be able to upload big files to nextclcoud via webdav in macos
Nextcloud Server version
28
Operating system
Debian/Ubuntu
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?
Configuration report
not relevant
List of activated Apps
not relevant
Nextcloud Signing status
not relevant
Nextcloud Logs
not relevant
Additional info
php8.2-fpm