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
As of now Keploy supports only client initiated calls, by listening on the client connection, incase if the connection request is using TLS it handles the it via creating TLS connection and acts as a proxy for communication between client and server.
However, incase of server initiated calls this fails as there's no listener on the server.
Why should this be worked on?
To solve this both client and server can be listened asynchronously and incase any connection packet is received via either end, it should proceed using that connection.
*For example, in SMTP calls, after TCP initiation, the server initiates a call to verify the client. Once verified, it proceeds to establish TLS via the client end.
Repository
keploy
The text was updated successfully, but these errors were encountered:
Is there an existing feature request for this?
Summary
Why should this be worked on?
*For example, in SMTP calls, after TCP initiation, the server initiates a call to verify the client. Once verified, it proceeds to establish TLS via the client end.
Repository
keploy
The text was updated successfully, but these errors were encountered: