Skip to content
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

Add self-check for api/status after the WebHost has been started #1

Open
michaelschnyder opened this issue Mar 16, 2017 · 0 comments
Open
Labels
Milestone

Comments

@michaelschnyder
Copy link
Member

michaelschnyder commented Mar 16, 2017

The WebHost should try to connect to himself in order to make sure the HttpListener has been able to register all the http prefixes and the API is available at the specified route.

This is easy for simple registrations like "http://localhost:80" but we probably need some more logic to also test registrations in the format http://0:0:0:0:80 or http://*:80. See: https://msdn.microsoft.com/en-us/library/system.net.httplistener(v=vs.110).

To connect back to the API, the Client Library of WebAPI could be used (probably needs additional IL-Merging) or the default TCP Stack from .NET

@michaelschnyder michaelschnyder added this to the 1.1.0 milestone Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant