mirror of
https://github.com/nextcloud/documentation.git
synced 2025-10-26 11:18:02 +00:00
1a3c860092
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> |
||
|---|---|---|
| .. | ||
| ai | ||
| configuration_database | ||
| configuration_files | ||
| configuration_mimetypes | ||
| configuration_server | ||
| configuration_user | ||
| file_workflows | ||
| gdpr | ||
| groupware | ||
| images | ||
| installation | ||
| issues | ||
| maintenance | ||
| office | ||
| reference | ||
| release_notes | ||
| apps_management.rst | ||
| conf.py | ||
| contents.rst | ||
| index.rst | ||
| make.bat | ||
| Makefile | ||
| release_notes.rst | ||
| release_schedule.rst | ||