> Hi,
>
> Please find here a fix for:
> 8262027: Improve how HttpConnection detects a closed channel when
> taking/returning a connection to the pool
>
> While writing a new test to verify that it was possible to handle proxy *and*
> server authentication manually when both proxy and server req
On Fri, 19 Feb 2021 19:34:26 GMT, Michael McMahon wrote:
>> There's no guarantee that the proxy will have read all the bytes sent by the
>> client - even if it attempts to drain the connection. So the only sane
>> reaction if you're not going to parse the request body is to close the
>> connec
On Thu, 18 Feb 2021 21:43:00 GMT, Alex Menkov wrote:
> The fix also partially fixes JdwpAttachTest failures (JDK-8253940).
> The failures are caused by network configuration changes during test
> execution ("global" IPv6 addresses disappears from interface).
> To minimize chances of intermittent
On Wed, 13 Jan 2021 06:19:18 GMT, Clive Verghese wrote:
> Redo for 8237578: JDK-8214339 (SSLSocketImpl wraps SocketException) appears
> to not be fully fixed
>
> This also fixes JDK-8259516: Alerts sent by peer may not be received
> correctly during TLS handshake
This pull request has now bee
On Mon, 22 Feb 2021 17:34:03 GMT, Daniel Fuchs wrote:
>
>
> I don't see any specific issue with the proposed change but I don't know the
> JDWP tests enough to provide more feedback than that. Do you have special
> test cases for the IPv6 loopback? AFAIU this code here will filter it out?
Go
> The fix also partially fixes JdwpAttachTest failures (JDK-8253940).
> The failures are caused by network configuration changes during test
> execution ("global" IPv6 addresses disappears from interface).
> To minimize chances of intermittent failures like this java.net tests use
> only link-loc
