You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting the port to 0 in the config, starts the server on a random port.
Alas, it seems there is no way to retrieve the port where the service was eventually bound to, currently.
It would be nice if one could use a shared map, say "webserver.config", to query that information (and more?) from the web-server. That would be especially useful in test cases where you don't want to depend on a static port setting.
The text was updated successfully, but these errors were encountered:
Setting the port to 0 in the config, starts the server on a random port.
Alas, it seems there is no way to retrieve the port where the service was eventually bound to, currently.
It would be nice if one could use a shared map, say "webserver.config", to query that information (and more?) from the web-server. That would be especially useful in test cases where you don't want to depend on a static port setting.
The text was updated successfully, but these errors were encountered: