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

Production should bind to port 8080, not 80 #1455

Closed
jdmcd opened this issue Jan 26, 2018 · 2 comments
Closed

Production should bind to port 8080, not 80 #1455

jdmcd opened this issue Jan 26, 2018 · 2 comments
Assignees
Milestone

Comments

@jdmcd
Copy link
Member

jdmcd commented Jan 26, 2018

Binding to port 80 makes the process privileged which is unsafe

@pedantix
Copy link
Member

I think 8080 is a much better port to bind to by default. This, of course, can and should be overridable via arguments and configuration, that said port 80 should be "opt in" not "opt out". I actually contemplated a "forceSSL" flag as a configuration option but figured that it probably was somewhere that I just could not find.

@tanner0101
Copy link
Member

This was changed back to 8080 a while back. 👍

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

No branches or pull requests

4 participants