What problem are you trying to solve?
Currently, it's not possible (or easy) to whitelist ports on localhost. The only way available is to whitelist ports one by one. It's not possible to whitelist all ports on localhost (0 only works on macOS, not on Linux). In many cases (usually tests), a process listens on a random free port and then allows the client to connect to it. Another way to think about this is to allow a child process to listen on any port and allow communication with those ports, but this is also not possible today.
What would you like to see?
- Port range support
- 0 works reliably on macOS and Linux
- A child process is allowed to connect to ports on which it listens
What have you tried instead?
No response
How is this blocking you?
None
Additional context
No response
What problem are you trying to solve?
Currently, it's not possible (or easy) to whitelist ports on localhost. The only way available is to whitelist ports one by one. It's not possible to whitelist all ports on localhost (0 only works on macOS, not on Linux). In many cases (usually tests), a process listens on a random free port and then allows the client to connect to it. Another way to think about this is to allow a child process to listen on any port and allow communication with those ports, but this is also not possible today.
What would you like to see?
What have you tried instead?
No response
How is this blocking you?
None
Additional context
No response