This repository was archived by the owner on Dec 18, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 523
Establish which ipv4/ipv6 socket addresses to open #7
Comments
This is a super old bug but it was in the alpha4 milestone, so moving to RC1 to reevaluate. |
Duplicate of #231 |
this and aspnet/Announcements#80 have the milestone as rc1/rc2, but based on the description of aspnet/Announcements#80, should they be beta8 instead / in addition? |
Updated. The initial change was in beta8: f0137b7 |
var remoteIp = context.Connection.RemoteIpAddress.ToString(); |
I Used asp.net 5, VS beta8 and dnx beta8 get null remote ip, when I use dnx beta7,it is ok to get the remote ip address,I am confused. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Assumption is localhost should be ipv4+ipv6 loopback, numeric addresses should be that address in ipv4 or ipv6, and any other name including + and * should be ipv4+ipv6 any ip
The text was updated successfully, but these errors were encountered: