Skip to content

Kestrel no longer ignores the hostname supplied to --server.urls #80

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

Open
halter73 opened this issue Oct 14, 2015 · 1 comment
Open

Comments

@halter73
Copy link
Member

Take the following project.json snippet:

"commands": {
    "kestrel": "Microsoft.AspNet.Server.Kestrel --server.urls http://localhost:5000"
}

Prior to beta8, Kestrel would bind to IPAddress.Any even if localhost was specified via server.urls meaning that Kestrel would respond to remote requests. Starting in beta8, this bug has been fixed, so Kestrel will only respond to loopback requests if localhost is specified.

To continue responding to remote requests, specify "*" instead of "localhost" when you provide server.urls. Technically, any hostname that isn't "localhost" or a valid IPv4 or IPv6 address will cause Kestrel to bind to all network interfaces. Ex:

"commands": {
    "kestrel": "Microsoft.AspNet.Server.Kestrel --server.urls http://*:5000"
}
@aspnet aspnet locked and limited conversation to collaborators Oct 14, 2015
@halter73
Copy link
Member Author

Please use aspnet/KestrelHttpServer#7 for feedback and discussion.

@Eilon Eilon added this to the 1.0.0-rc1 milestone Oct 14, 2015
@Tratcher Tratcher modified the milestones: 1.0.0-beta8, 1.0.0-rc1 Nov 10, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants