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
For HTTP, on closing a connection (server or client), the associated HTTP content stream (request content for server and response content for client) is sent an onComplete(). This behavior should be modified as follows:
If the request/response is not complete (we have not yet received LastHttpContent) at the time of connection close, it should result in invoking onError on the content stream. This is required as not doing so will result in clients/servers receiving incomplete content.
If the request/response is completed, there is no change required.
The current behavior also results in wrong metrics on inflightRequests
The text was updated successfully, but these errors were encountered:
ReactiveX#248 (Connection close cancels pending writes): Now only cancelling when a pooled connection is returned to the pool.
ReactiveX#249 (`BytesInspector` does not record events for `ByteBufHolder` and `FileRegion`): Recording events for ByteBufHolder and FileRegion
ReactiveX#250 (Connection closing and content stream behavior): Send error on content stream if the request/response is not completed on server/client.
ReactiveX#251 (Metric events for Request content source error and request write failure): Added metrics
For HTTP, on closing a connection (server or client), the associated HTTP content stream (request content for server and response content for client) is sent an
onComplete()
. This behavior should be modified as follows:LastHttpContent
) at the time of connection close, it should result in invokingonError
on the content stream. This is required as not doing so will result in clients/servers receiving incomplete content.The current behavior also results in wrong metrics on
inflightRequests
The text was updated successfully, but these errors were encountered: