| 17 Jun 2020 |
 Stefan | I will check it out later in the variantions you just poostet | 16:59:07 |
 Linda | In reply to @lindalap:matrix.org
IANA doesn't have a service name for port 8448, so at best it's '( sport = :http-alt or sport = :8448 )' and that is unfortunately because of a Synapse design decision. Imagine if sport = :http-alt would've covered both client and server ports. | 16:59:28 |
| Linda | (ports 8080 and 8008) | 16:59:50 |
| Linda | In reply to @lindalap:matrix.org
IANA doesn't have a service name for port 8448, so at best it's '( sport = :http-alt or sport = :8448 )' * and that is unfortunately because of a Synapse Matrix spec design decision. Imagine if sport = :http-alt would've covered both client and server ports. | 17:02:01 |
| Linda |
This will work with well.known, SRV-records and nginx.
Set up well.known
same with the hyphen, s/well\.known/.well-known/
| 17:06:34 |
| Linda | *
This will work with well.known, SRV-records and nginx.
Set up well.known
same with the hyphen, s/well\.known/.well-known/
| 17:06:49 |
| Linda |
So if you navigate to https://example.com/.well-known/matrix.server it may try to download the server file or show it directly.
s/matrix\.server/matrix\/server/
| 17:09:37 |
| Linda | *
So if you navigate to https://example.com/.well-known/matrix.server it may try to download the server file or show it directly.
s/matrix\.server/matrix\/server/
should be https://example.com/.well-known/matrix/server
| 17:09:53 |
| Linda | and I don't like using example.com in documentation, bots (like in chats) may crawl links and visit them and hit a real server unnecessarily | 17:10:21 |
| Linda | for an error | 17:10:24 |
| Linda | host.example is my preference, or homeserver.example | 17:10:43 |
| Linda | particularly, I feel like Synapse homeservers crawls links posted because of embedded URL previews | 17:11:25 |
| Linda | natrius.example 😁 | 17:13:18 |
| Stefan | Well... | 17:29:14 |
| Stefan | example.com is exactly for that purpose, to be honest. | 17:29:25 |
| Stefan | 
Download image.png | 17:29:43 |
| Stefan | example.com is provided by iana themself https://www.iana.org/domains/reserved | 17:30:42 |
| Stefan | But i understand what you mean. | 17:30:52 |
| Stefan | In reply to @lindalap:matrix.org
This will work with well.known, SRV-records and nginx.
Set up well.known
same with the hyphen, s/well\.known/.well-known/
Doine | 17:32:47 |
| Stefan | In reply to @lindalap:matrix.org
So if you navigate to https://example.com/.well-known/matrix.server it may try to download the server file or show it directly.
s/matrix\.server/matrix\/server/
should be https://example.com/.well-known/matrix/server
Done | 17:32:54 |
| Linda | In reply to @natrius:matrix.org
example.com is exactly for that purpose, to be honest. I know. But .example TLD was also specially reserved for documentation, without causing load on the root resolvers (particularly .com), the example.com domain, etc. | 17:35:19 |
| Linda | Hyperlink target preloading. 😁 | 17:35:42 |
| Stefan | Dunno | 17:37:56 |
| Stefan | https://tools.ietf.org/html/rfc6761 | 17:37:57 |
| Stefan | 6.5 | 17:38:00 |
| Stefan | states the example domains SHOULD be used like normal names in every application | 17:38:18 |
| Linda | Indeed, and not treated specially, so they create DNS queries. | 17:38:54 |
| Linda | https://tools.ietf.org/html/rfc2606#section-2
aka BCP 32, | 17:41:18 |
| Linda | BCP 32 also mentions those IANA domain names, "which can be used as examples". "Can be".
".example" is recommended
| 17:42:48 |
| Stefan |
".example" is recommended for use in documentation or as examples.
| 17:44:02 |
