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
Ipv6 #11
Comments
Good idea. Will do. Of course, you can also go ahead and make a PR if you would like to take a stab at this yourself. |
I just discovered, that it is already capable of running Ipv6, just pass e.g.
(please note the "wrong" format:
it should be There is a problem though.
|
One more note: If it is an IPv6, the URL should be displayed like this: `http://[::]:8080'. |
@hellow554 Thanks for considering this so thoroughly! About your 1.: I don't quite understand. How would you even go about binding on both interfaces if you provide an IPv6? It could just be that an interface does not even have an IPv4 even if it has an IPv6. Basically, I think that if an explicit IPv4 or IPv6 is given, we should not try to bind on anything except those provided. I think
|
Fixed in v0.2.0. |
You are currently only allow Ipv4 access to the host, but no IPv6.
I would like to see either a command line argument to enable one/both or make dual stack the default :)
The text was updated successfully, but these errors were encountered: