Permanent changes to the web server configuration (.htaccess)

Some provider environments do not allow you to change the basic web server configuration to allow only https access. A common work-around is to set up a redirection in the .htaccess file in the root directory of the webapp (Nextcloud).

Unfortunately, when upgrading the software of Nextcloud, it happens again and again that the .htaccess file is replaced. As a result, this redirection is lost again.
I see this as a security risk, since the login data of an inexperienced users may be transmitted unencrypted.

Although I try to check and update the .htacces file after each upgrade. But, sometimes this get forgotten.

Is there any way to preserve these customizations in the .htaccess file across software upgrades?
I can imagine this in different ways. For example,

• the .htaccess file has a marked area that is transferred to the new .htaccess file.
• a small app handles extensions to the .htaccess file (similar to the app Custom CSS). However, the upgrade process should add these extensions before the first access to Nextcloud.

Regards,
Friedbert

Start by examining how the updater replaces the root .htaccess file during software upgrades. Define how custom HTTPS-redirection changes can survive that replacement, then verify the behavior across an upgrade without losing the existing customization.