This hides the response headers coming from nextcloud, which keeps the headers from swag's ssl.conf. The values for the headers are the same, so there is no conflict, but if nextcloud's response headers are not hidden then both nextcloud and swag's headers are included in the response, and duplicate response headers causes issues.
Solved discord thread https://discord.com/channels/354974912613449730/1122102501672484935
This hides the response headers coming from nextcloud, which keeps the headers from swag's
ssl.conf. The values for the headers are the same, so there is no conflict, but if nextcloud's response headers are not hidden then both nextcloud and swag's headers are included in the response, and duplicate response headers causes issues.