fix for element wich generate cors error on FFX

[rosbeef]

fix element to works on firefox

Problem

• element dosent ork on ffx for cors security reason

Solution

• add cors header to ngix.conf that alow * on specific wellknown

PR Status

• [x] Code finished and ready to be reviewed/tested
• [ ] The fix/enhancement were manually tested (if applicable)

Automatic tests

Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

[Josue-T]

Hello,

Are you sure that the patch should be on this file and not in the server_name.conf ?

[rosbeef]

Sorry I search in my files an yes it is the right place

[rosbeef]

Server_name is, as I understand the nginx conf for usersid domain extension usually domain.tld Nginx.conf is for the server subdomain name usually matrix.domain.tld

[Josue-T]

Well,

I'm a bit confused, because we already have a well-known configuration for the client here. Could you please provide me matrix documentation who say that theses informations should be on the synapse domain. And if it's the case we should move all the client config to the synapse domain and not add a new config.

[rosbeef]

Hello sorry i'm travelling back and can not respond you well. I found nothing inside matrix docs but did not search well. The only thing I can tell you is that from ffx 101 I couldn't connect due to a cors error, I needed to add this exception to the matrix host server domain (not the user domain (neither the client domain)) which are different in my configuration.

[rosbeef]

seem to not be needed anymore