Possible problem with redirect logic

If my cluster is configured to have the following members: localhost:1000, localhost:1001, localhost:1002

The following code will not redirect to the leader properly since the port that is used for the redirect is not the leader port:

internal Task Redirect(HttpContext context)
{
    if (context.Request.Path.StartsWithSegments(pathMatch, StringComparison.OrdinalIgnoreCase))
    {
        var leader = cluster.Leader;
        if (leader is null)
        {
            context.Response.StatusCode = StatusCodes.Status503ServiceUnavailable;
            return Task.CompletedTask;
        }
        else if (leader.IsRemote)
        {
            return redirection(context.Response, new UriBuilder(context.Request.GetEncodedUrl()) { Host = leader.Endpoint.Address.ToString(), Port = applicationPortHint ?? context.Connection.LocalPort }.Uri);
        }
    }

    return next(context);
}

should this not use something like the following?

new UriBuilder(context.Request.GetEncodedUrl()) { Host = leader.Endpoint.Address.ToString(), Port = leader.Endpoint.Port }.Uri)

[sakno]

From my point view, your dev and test environment should be close to the production environment to eliminate potential infrastructure problems during deployment.

[sakno]

I checked it on Windows, you can register additional Loopback Adapters through Control Pane as described here.