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
When a protocol error happens (as part of protocol version negotiation or not), the proxy invokes the shutdown mechanism for that connection after sending the response to the write queue but due to #68 the client may see the connection closed without the protocol error actually being sent.
Due to this, the proxy should at least not shutdown the connection when a protocol error happens while #68 is not addressed.
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: ZDM-411
The text was updated successfully, but these errors were encountered:
When a protocol error happens (as part of protocol version negotiation or not), the proxy invokes the shutdown mechanism for that connection after sending the response to the write queue but due to #68 the client may see the connection closed without the protocol error actually being sent.
Due to this, the proxy should at least not shutdown the connection when a protocol error happens while #68 is not addressed.
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: ZDM-411
The text was updated successfully, but these errors were encountered: