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
I am able to connect my client to the proxy even if the upstream server socket is not accepting connections. This means I cannot test all my use cases (e.g. server is absent) because the proxy will accept the connection on behalf of the upstream. When I go to send data it errors, but I would rather the socket is not accepted if upstream is down.
An alternative would be if the upstream rule is disabled then the proxy does not accept connections for that rule.
Behaving in this manner would change the code in which the server accepts connections. During the acceptance, the server would either:
attempt a connection to upstream and refuse the client if that server could not be established, or
verify the rules and if enabled was false it would reject the connection
The text was updated successfully, but these errors were encountered:
Idea how to toggle automatically, it is when the Upstream gracefully shutdown the connection, then server should switch stated to Disabled. But it would require user to toggle back in case upstream restored.
I am able to connect my client to the proxy even if the upstream server socket is not accepting connections. This means I cannot test all my use cases (e.g. server is absent) because the proxy will accept the connection on behalf of the upstream. When I go to send data it errors, but I would rather the socket is not accepted if upstream is down.
An alternative would be if the upstream rule is disabled then the proxy does not accept connections for that rule.
Behaving in this manner would change the code in which the server accepts connections. During the acceptance, the server would either:
The text was updated successfully, but these errors were encountered: