element-web: Unable to deploy .well-known file to disable E2EE by default. Consider config.json alternative

Description

Trying to implement https://github.com/vector-im/riot-web/pull/13914 I run into an issue.

I’ve added the json section in https://matrix.corporate.local/.well-known/matrix/client:

{"m.homeserver": {"base_url": "https://matrix.corporate.local/"}, "m.identity_server": {"base_url": "https://matrix.corporate.local"}, "im.vector.riot.e2ee": {"default": false}}

and also in config.json of riot

    "default_server_config": {
        "m.homeserver": {
            "base_url": "https://matrix.corporate.local",
            "server_name": "Corporate Local"
        },
        "m.identity_server": {
            "base_url": "https://matrix.corporate.local"
        },
        "im.vector.riot.e2ee": {
            "default": false
        }

Now my question is if that isn’t enough and if not if we could please have the option to specify this via config.json of riot as well since that doesn’t seem to work right now(?).

Because our synapse is running on matrix.corporate.local in a corporate environment where corporate.local points to the active directory servers on which I can’t and also don’t want to run a webserver to just serve a .well-known for the domain.

Steps to reproduce

• Have a setup like described above
• Try to implement https://github.com/vector-im/riot-web/pull/13914
• See Riot still creating DMs and rooms with encryption enabled by default

Version information

• Platform: web (in-browser)

For the web app:

• Browser: Chrome, Firefox latest versions
• OS: Windows, Linux
• URL: self hosted, latest riot web 1.6.6-rc.1