Commit Graph

29 Commits

Author SHA1 Message Date
Array in a Matrix
0a022db256
grammar correction
the word "both" would refer to only 2 urls in this context
2022-10-21 00:52:48 -04:00
Matt Holt
9e87f9d885
Update configuring-well-known.md 2022-07-20 12:10:34 -06:00
Matt Holt
2e02e694b4
Update configuring-well-known.md
Make use of `example.com` more consistent (replace `DOMAIN`) and simplify Caddy 2 config. Remove Caddy 1 config since Caddy 1 is long past EOL.
2022-07-19 16:31:01 -06:00
Slavi Pantaleev
78b5be4a26 Do not generate /.well-known/matrix/support unless explicitly asked to
Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1931
2022-07-18 12:54:45 +03:00
Slavi Pantaleev
3f7498da5a Fix matrix_homeserver_admin_contacts example
Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1931

This does 2 things:

- it fixes the syntax for `matrix_id`. Starting strings with `@` is
  invalid YAML, so such strings need to be wrapped in single or double
  quotes
- it makes use of the `matrix_domain` variable instead of hardcoding the
  domain name. This should be more and mistake-proof (typos or people
  mistaking their domain - matrix. vs base domain)
2022-07-18 12:49:53 +03:00
teutates
018ca75d48
Implement MSC 1929 Homeserver Admin Contact (#1931)
* Implement MSC 1929 Homeserver Admin Contact
Fixes #1612

For details to the proposed (not accepted yet) MSC, see:
https://github.com/matrix-org/matrix-spec-proposals/blob/hs/proposal-admin-contact-1/proposals/1929-admin-contact.md

* Implement feedback from PR #1931

* Implement feedback from PR #1931

* Fix mixed indentation
2022-07-18 12:28:59 +03:00
freiit
02cc201f14
Add configuration instruction for AWS CloundFront 2022-07-01 12:28:10 +02:00
brush
3499b9cd03
Update configuring-well-known.md 2022-05-13 03:45:08 -07:00
brush
34de6c9c66
Update configuring-well-known.md 2022-05-13 03:44:16 -07:00
Arkonos
527f5bc469 clarifying where well-known files are created 2022-05-08 21:56:14 +02:00
Arkonos
6abdb6e6f0 clarifying reverse proxying of well-known files 2022-05-08 21:33:46 +02:00
maximilianschmelzer
5ddd7d9ea1
Update configuring-well-known.md 2021-07-24 13:12:32 +02:00
Martha Sokolska
c3fcaa5afe
Add Netlify instructions 2021-02-19 02:37:01 +01:00
Slavi Pantaleev
c6ab1c6a90 Riot is now Element
Fixes #586 (Github Issue)
2020-07-17 11:31:20 +03:00
Slavi Pantaleev
3452347648 Suggest base domain serving in configuring-well-known.md
Fixes #545 (Github Issue).
2020-06-24 09:42:41 +03:00
kristbaum
201292cdc5
typo 2020-06-07 19:56:12 +02:00
André Sterba
966b74e74f Add caddy 1 well-known example
Adjust params
2020-05-01 14:43:31 +02:00
Sean O'Neil
eb8e162ac2
Update Caddy example in configuring-well-known to Caddy version 2 2020-04-05 11:36:08 -07:00
Arehandoro
d7343389ec
Update configuring-well-known.md 2019-09-23 16:44:13 +01:00
Slavi Pantaleev
2e16257e50 Do not ask for _matrix._tcp SRV records anymore
With most people on Synapse v0.99+ and Synapse v1.0 now available,
we should no longer try to be backward compatible with Synapse 0.34,
because this just complicates the instructions for no good reason.
2019-06-12 14:51:10 +03:00
Slavi Pantaleev
e6fecd51d5 Explain DNS SRV vs /.well-known/matrix/server better
Hopefully, we no longer lead people to believe that DNS SRV
records are going away forever and for all use-cases.

Fixes #156 (Github Issue)
2019-05-05 11:04:52 +03:00
Slavi Pantaleev
c545d3eb85 Add support for serving base domain via matrix-nginx-proxy 2019-03-12 23:01:16 +02:00
Slavi Pantaleev
f4fa03d4b9 Re-iterate where one can find the well-known files 2019-02-07 19:43:00 +02:00
Slavi Pantaleev
f6ebd4ce62 Initial work on Synapse 0.99/1.0 preparation 2019-02-05 12:09:46 +02:00
Slavi Pantaleev
9dad4c7c2d Fix /.well-known/matrix/client for CORS
This is provoked by Github issue #46.

No client had made use of the well-known mechanism
so far, so the set up performed by this playbook was not tested
and turned out to be a little deficient.

Even though /.well-known/matrix/client is usually requested with a
simple request (no preflight), it's still considered cross-origin
and [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)
applies. Thus, the file always needs to be served with the appropriate
`Access-Control-Allow-Origin` header.

Github issue #46 attempts to fix it at the "reverse-proxying" layer,
which may work, but would need to be done for every server.
It's better if it's done "upstream", so that all reverse-proxy
configurations can benefit.
2018-11-29 09:13:25 +02:00
Slavi Pantaleev
4bb8d4cb60 Fix up well-known documentation a bit 2018-10-29 22:39:04 +02:00
Slavi Pantaleev
d0c2ef10e4 Add self-check command 2018-10-21 12:58:25 +03:00
anadahz
12d96f5e23 Add sample .well-know config for Caddy 2018-10-19 15:22:27 +01:00
Slavi Pantaleev
0d0ccde286 Add Service Discovery (/.well-known/matrix/client) support 2018-09-17 10:51:46 +03:00