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

Move federation traffic from port 8448 to 443 as a default #1577

Open
turt2live opened this issue Jun 16, 2023 · 2 comments
Open

Move federation traffic from port 8448 to 443 as a default #1577

turt2live opened this issue Jun 16, 2023 · 2 comments
Labels
A-S2S Server-to-Server API (federation) feature Suggestion for a significant extension which needs considerable consideration

Comments

@turt2live
Copy link
Member

per #1576 (comment)

@turt2live turt2live added feature Suggestion for a significant extension which needs considerable consideration A-S2S Server-to-Server API (federation) labels Jun 16, 2023
@nisbet-hubbard
Copy link

nisbet-hubbard commented Jul 31, 2023

443 is also required on homeservers behind Cloudflare (which doesn’t offer 8448 on free tier), currently achieved through .well-known delegation.

@6543
Copy link

6543 commented Aug 4, 2023

as #1576 is registered 🎉
and I know that large scale installation can benefit from c2s and s2s trafic seperation ... I think we should not deprecate it, instead support both (smal install on same port, bit install do seperate trafic)

so about the "default" port I dont know, I think the spec should handle them equaly and the server implementation should decide what there best default value is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-S2S Server-to-Server API (federation) feature Suggestion for a significant extension which needs considerable consideration
Projects
None yet
Development

No branches or pull requests

3 participants