Nginx resets all response headers in a location block, if it contains any "add_header" directive. When setting the "Cache-Control" header for static assets, this was originally worked around by using the "expires" directive instead. https://github.com/nextcloud/documentation/pull/8083 however added the "immutable" flag for assets with "v=" query parameter and broke all other response headers for assets that way.
This commit fixes this by re-adding all reponse headers explicitly for those assets. Originally those doubled code was removed thanks to using "expires", but I see no way to have both: the "immutable" flag as well as avoiding doubled headers via "expires" directive.
Additionally, this commit avoids the trailing comma and space in the Cache-Control header for assets without "v=" query parameter, and adds sets the wasm MIME type in a cleaner/more consistent way together with js/mjs, and rephrases the broken comment sentence.
Signed-off-by: MichaIng <micha@dietpi.com>
`mail_smtpdebug` was being described in two places, one of which was incomplete (it didn't note the requirement to also change `loglevel` to `0`... leading to confusion).
* Removes the inaccurate spot and moves the accurate one into its place so there are no longer two debug logging sections.
Signed-off-by: Josh <josh.t.richards@gmail.com>
There are downsides to changing `data-fingerprint` after recovering from a backup:
* Conflicts are shown to the user rather than automatically resolved.
* Files will be kept even if they were deleted on one side.
Explain those so the admin can make an informed decision.
Signed-off-by: Max <max@nextcloud.com>
- Since 27.1.2 and 26.0.8 ocm-provider is not a dir anymore, but
implemented in a usual Controller. Nginx webserver config requires
adjustemnts.
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Apache's default for this changed from 0 (unlimited) to 1 GiB. This impacts non-chunking client transactions.
Resolves: #35778 and #37695 and documents needed adjustments applicable to various others like https://github.com/nextcloud/docker/issues/1796
Signed-off-by: Josh Richards <josh.t.richards@gmail.com>
If we recommend a Debian operating system, it would be better to use a version that already ships a php version that is supported by NC.
https://wiki.debian.org/PHP#Available_versions
Not sure if you do some specific tests on a Debian setup and to claim to support it, you would need to adjust the version as well.
Perhaps backport to NC26 as well.
Signed-off-by: tflidd <tflidd@aspekte.net>
The `.htaccess` rules should not have the starting slash otherwise they
will never get matched. When running the mod_rewrite in .htaccess, the
path is already sanitized and leading slashes stripped.
Document also that this is not the case when the rules are used directly
from the main apache2 configuration the leading slash is present always,
which led to some edit wars of this documentation in the past as it was
not well explained (#8093, #3811).
This matches the code shipped with the .htaccess in the nextcloud server:
https://github.com/nextcloud/server/blob/master/.htaccess
Signed-off-by: Jakub Jelen <jakuje@gmail.com>
