You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SRV records would be very nice, I'll look into this myself when I have the time
The idea is quite simple, put SRV record at _aurum._tcp.example.com, pointing to https://aurum.example.com. This should then allow you to use example.com as your host in aurum, which it somehow resolves itself to the actual domain.
I've decided to make it point to the full domain, including protocol to support unusual ports and http instead of https for internal use.
The text was updated successfully, but these errors were encountered:
Another possibility is support for Well-Known URIs [1], under for example https://example.com/.well-known/aurum, Matrix uses both of these techniques [2] so we can use that for inspiration.
Well-Known URIs would require a way to check if the original domain is an Aurum server or a normal http server, since unlike Matrix both run on http(s). One solution for that would be to have the aurum server also have a "valid" Well-Known URI, which simply points to itself, like "uri": "self", or the full uri if we have that readily available.
Edit: Upon looking at matrix' documentation a bit more it seems like it could be done as described in Resolving Server Names, that way the server itself would not need a Well-Knows URI for itself. This might however make things a bit more slow, since we will first need to exhaust all other options before just assumint the provided uri is the actual target
SRV records would be very nice, I'll look into this myself when I have the time
The idea is quite simple, put SRV record at
_aurum._tcp.example.com
, pointing tohttps://aurum.example.com
. This should then allow you to useexample.com
as your host in aurum, which it somehow resolves itself to the actual domain.I've decided to make it point to the full domain, including protocol to support unusual ports and http instead of https for internal use.
The text was updated successfully, but these errors were encountered: