-
Notifications
You must be signed in to change notification settings - Fork 39
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
Change default replay port from 5000 #752
Comments
@ibnesayeed Is there any opposition to picking a new default port number? If not, can you suggest one that would be appropriate? |
This is such an unpleasant behavior by a big company who ignores what has already been used by a popular web server library by default for so long. I think it will be affecting many developers and users of locally running server-based applications that it is not a problem that concerns only us. That being said, I am okay if we decide to change to a different default port, but we might want to look around and see how others or dealing with this. |
As discussed, let's move to use port 2016 as a default. https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers does not have an entry for this value though list a very crowded port 5000. Any issues in moving forward with this @ibnesayeed? |
Let's go for it! |
PR #758 is ready for your review, @ibnesayeed |
A recent macOS update uses port 5000 by default for AirPlay Receiving. This is built into the system and turned on by default. While another port could easily be expressed at runtime, let's pick a new default.
The text was updated successfully, but these errors were encountered: