Re: How to handle .htaccess Invalid Hash on each Nextcloud Upgrade?

27 Oct 2023

      On 10/27/23 15:35, Martin Rys wrote:
...
I use nextcloud with nginx rather than Apache, but is there something 
preventing you from using the default htaccess and configuring what you need 
on the webserver side instead?
Yes,

You customize the .htaccess as part of the install if you install to the 
/nextcloud subdirectory, e.g.

   RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav/ [R=301,L]
   RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav/ [R=301,L]

And then arch includes the following at the end:

#### DO NOT CHANGE ANYTHING ABOVE THIS LINE ####

ErrorDocument 403 /nextcloud/index.php/error/403
ErrorDocument 404 /nextcloud/index.php/error/404
<IfModule mod_rewrite.c>
   Options -MultiViews
   RewriteRule ^core/js/oc.js$ index.php [PT,E=PATH_INFO:$1]
   RewriteRule ^core/preview.png$ index.php [PT,E=PATH_INFO:$1]
   RewriteCond %{REQUEST_FILENAME} 
!\.(css|js|mjs|svg|gif|png|html|ttf|woff2?|ico|jpg|jpeg|map|webm|mp4|mp3|ogg|wav|wasm|tflite)$
   RewriteCond %{REQUEST_FILENAME} !/core/ajax/update\.php
   RewriteCond %{REQUEST_FILENAME} !/core/img/(favicon\.ico|manifest\.json)$
   RewriteCond %{REQUEST_FILENAME} !/(cron|public|remote|status)\.php
   RewriteCond %{REQUEST_FILENAME} !/ocs/v(1|2)\.php
   RewriteCond %{REQUEST_FILENAME} !/robots\.txt
   RewriteCond %{REQUEST_FILENAME} !/(ocm-provider|ocs-provider|updater)/
   RewriteCond %{REQUEST_URI} !^/\.well-known/(acme-challenge|pki-validation)/.*
   RewriteCond %{REQUEST_FILENAME} !/richdocumentscode(_arm64)?/proxy.php$
   RewriteRule . index.php [PT,E=PATH_INFO:$1]
   RewriteBase /nextcloud
   <IfModule mod_env.c>
     SetEnv front_controller_active true
     <IfModule mod_dir.c>
       DirectorySlash off
     </IfModule>
   </IfModule>
</IfModule>

Of course with install to /nextcloud, you have to change the entries above the 
line.

-- 
David C. Rankin, J.D.,P.E.