Add support for multiple listen addresses: --bind #819
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe in detail the problem you had and how this PR fixes it
This PR allows for listening on multiple address/port combinations at the same time, which in turn fixes a problem where listening on port 80 (without
--allow-http
) would cause the HTTP=>HTTPS redirect to fail.--bind
can be supplied multiple times and is accepted in the form[HOST][:PORT]
. If the host or the port is not supplied, they will be filled with the default values0.0.0.0
andprocess.env.PORT || 8443
. If the user is using the now deprecated--host
and--port
arguments, they will be translated to a--bind
argument automatically.Additionally, you now cannot use
--host
/--port
and--bind
at the same time, and you cannot use--bind
and--socket
at the same time now. This will result in an error and code-server exiting.A warning is printed when the user listens on
address:80
but notaddress:443
when--allow-http
is false.Is there an open issue you can link to?
#737