It was removed from the config in #9188, but forgotten for the static assets block.
In addition, the date added with #12100 was is added to the subdir config as well, for consistency.
Signed-off-by: MichaIng <micha@dietpi.com>
To be in compliance with RFC6797 and https://hstspreload.org/, line 31 about the Strict-Transport-Security (HSTS) Header should have a minimum max-age of 31536000 seconds, and not have a ";" symbol at the end.
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>
- 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>
Move the `root` directive more to the top. That way all the
fields that need to be changed are in one place.
Signed-off-by: Christian Tacke <8560110+ChristianTacke@users.noreply.github.com>
Since Talk 13 (and thus Nextcloud 23) WebAssembly (.wasm) and TensorFlow
Lite (.tflite) files need to be loaded from the web server to provide
certain features (like the background blur in the WebUI).
Those files can be treated in a similar way to other static resources,
and there should not be any problem caching or compressing them.
However, as compressed TensorFlow Lite files are only ~12% smaller,
the compression directive depends on the MIME type and there is no
standard MIME type for TensorFlow Lite files, for now only WebAssembly
files are compressed.
Depending on the setup "application/wasm" may not be associated with
".wasm" files, so the directive was added just in case, as the
compression is enabled through the MIME type and, besides that, the
browsers log a warning if the expected MIME type is not returned.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
- Follow the .htaccess and exclude .well-known redirects for ACME challenges and PKI validation, which are not handled by Nextcloud, and handle requests for `/remote`
- Preserve the query string when redirecting .well-known URIs.
- Separate the example config files from nginx.rst
Signed-off-by: MichaIng <micha@dietpi.com>
