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

Prioritize port 443 #404

Closed
wants to merge 1 commit into from
Closed

Prioritize port 443 #404

wants to merge 1 commit into from

Conversation

link2xt
Copy link
Contributor

@link2xt link2xt commented Aug 23, 2024

Port 443 has more chance to work
in networks where ports other than 80 and 443
are dropped.
Otherwise user has to wait for other ports
to time out before trying port 443.

Port 443 has more chance to work
in networks where ports other than 80 and 443
are dropped.
Otherwise user has to wait for other ports
to time out before trying port 443.
@link2xt
Copy link
Contributor Author

link2xt commented Aug 23, 2024

hopefully this does not break thunderbird autoconfiguration, hope it tries other ports as well

@link2xt
Copy link
Contributor Author

link2xt commented Aug 23, 2024

I tested, it breaks Thunderbird. Thunderbird configures port 443 and then fails to connect, also if you then click "configure manually" it shows port 443.

@link2xt link2xt closed this Aug 23, 2024
@link2xt
Copy link
Contributor Author

link2xt commented Aug 23, 2024

For known providers we can prioritize via provider DB, and long-term this should be fixed by parallelizing connection attempts.

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

Successfully merging this pull request may close these issues.

2 participants