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

Advice on transport ports #455

Closed
mnot opened this issue Dec 14, 2017 · 1 comment
Closed

Advice on transport ports #455

mnot opened this issue Dec 14, 2017 · 1 comment
Labels

Comments

@mnot
Copy link
Member

mnot commented Dec 14, 2017

Applications that use HTTP SHOULD use the default port for the URL scheme in use.

This isn't really necessary. I would instead say that the port number is in the URL and cite Initial URL Discovery for details.

Then explain that if you are bootstrapping from a bare hostname with .well-known, then this should assume the use of the default port for the scheme unless there are very good reasons. In particular, when it comes to using port numbers other than the default, you can note that there are privacy implications (it makes your protocol distinguishable) and deployment implications (some middleboxes might interfere with the operation of your protocol).

(from @martinthomson)

@mnot
Copy link
Member Author

mnot commented Feb 13, 2018

Does anything stop someone from saying "my application looks up the well-known HTTPS url on port nnnn..."?

Should it? (doing wellknownbis now...).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant