It's still problematic
If you set "write headers to configuration file" and then options as in this screenshot

Then both referrer policy are written to the htaccess file

Although only the second one will be used.

actually its a little more complicated than I wrote above. As sometimes you do only get the one line.

Its all very confusing. Writing headers to the file actually makes it more confusing (for me). Is it even compatible with setting headers for site or admin or both?

There is no way to delete all the headers from the htaccess. So once they have been written to the htaccess if you then disable that option no changes made to the settings will be applied

We also now have the situation that we have rules set in the htaccess, rules set in the plugin, and rules set in the component and no way to see in one place all the rules that are being applied. This will make debugging a faulty rule very hard.

Can we please open a separate issue for the htaccess issue, so we can keep this here to the suggested rename of the feature?

Although only the second one will be used.

Isn't that what force implies?

Can we please open a separate issue for the htaccess issue, so we can keep this here to the suggested rename of the feature?

Done here: #25716 so we can keep this on renaming the feature as suggested.

I have tested this item ✅ successfully on dd28fac

This makes sense and combined with the apache file no longer being edited I believe this solves the other part of the issue. Thanks!

Doc change Done.