Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SRV Record support #28

Open
J00LZ opened this issue Dec 11, 2020 · 2 comments
Open

SRV Record support #28

J00LZ opened this issue Dec 11, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@J00LZ
Copy link
Member

J00LZ commented Dec 11, 2020

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.

@J00LZ J00LZ added the enhancement New feature or request label Dec 11, 2020
@J00LZ J00LZ self-assigned this Dec 11, 2020
@NULLx76
Copy link
Member

NULLx76 commented Dec 11, 2020

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.

1: https://tools.ietf.org/html/rfc8615
2: https://github.com/matrix-org/synapse/blob/develop/docs/delegate.md#delegation

@J00LZ
Copy link
Member Author

J00LZ commented Dec 12, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants