Skip to content

Commit

Permalink
Minor changes to RELEASE_NOTES.txt
Browse files Browse the repository at this point in the history
  • Loading branch information
garydgregory authored Jan 24, 2025
1 parent b5e0439 commit 2e481b5
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions RELEASE_NOTES.txt
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
Release 5.3.3
------------------

This maintenance release fixes a defect in how async SSL sessions handles and overflow
condition when encrypting application data. There has also been several fixes for fringe
cases related to the handling of HTTP/1.1 async connections half-closed by the opposite
This maintenance release fixes a defect in how asynchronous SSL sessions handle an overflow
condition when encrypting application data. There have also been several fixes for edge
cases related to handling HTTP/1.1 asynchronous connections half-closed by the opposite
endpoint.


Expand All @@ -17,18 +17,18 @@ Change Log
the application (protocol) layer.
Contributed by Oleg Kalnichevski <olegk at apache.org>

* Bug fix: Corrected shutdown of async HTTP/1.1 connections half-closed by the opposite
* Bug fix: Corrected shutdown of asynchronous HTTP/1.1 connections half-closed by the opposite
endpoint.
Contributed by Oleg Kalnichevski <olegk at apache.org>

* Bug fix: Made shared output buffer #writeCompleted block until the end of stream has been
* Bug fix: Made shared output buffer #writeCompleted block until the end of a stream has been
written out.
Contributed by Oleg Kalnichevski <olegk at apache.org>

* HTTPCORE-775: Fixed handling SSLEngineResult#BUFFER_OVERFLOW of by Async SSLIOSession#write
* HTTPCORE-775: Fixed handling SSLEngineResult#BUFFER_OVERFLOW of by asynchronous SSLIOSession#write
Contributed by Andriy Redko <drreta at gmail.com>

* Bug fix: in some fringe cases the request may still be not fully completed while
* Bug fix: In some edge cases, the request may still not be fully completed while
the response has already been fully committed by the HTTP/1.1 stream handler. Connections
that cannot be kept alive must be closed only once both request and response streams are
fully complete.
Expand Down

0 comments on commit 2e481b5

Please sign in to comment.