RFR:8212114 Reconsider the affect on closed streams resulting from 8189366

Hi All, Please review the below fix. Webrev: http://cr.openjdk.java.net/~vtewari/8212114/webrev0.0/index.html bugId: https://bugs.openjdk.java.net/browse/JDK-8212114 this change the revert the effect of JDK-8189366,  restore the existing(SocketInputStream:available() will throw the socketExce

Re: RFR [12] 8211437: java.net.http.HttpClient hangs on 204 reply without Content-length 0

Updated webrev for this at http://cr.openjdk.java.net/~michaelm/8211437/webrev.2/index.html based on feedback below. I also made a change to the com.sun httpserver. It changes the recent fix related to the same issue such that by default the server will not send a content-length back, if the u

Re: RFR [12] 8211437: java.net.http.HttpClient hangs on 204 reply without Content-length 0

Hi Michael, Thanks for taking on all the feedback! MultiExchange.java: 254 if (bodyIsPresent(r)) { 255 IOException ioe = new IOException( 256 "unexpected content length header with 204 response"); 257 exch.cancel(); 258 return MinimalFuture.failedFut

Re: RFR [12] 8211437: java.net.http.HttpClient hangs on 204 reply without Content-length 0

Hi Daniel, On 18/10/2018, 16:01, Daniel Fuchs wrote: Hi Michael, Thanks for taking on all the feedback! MultiExchange.java: 254 if (bodyIsPresent(r)) { 255 IOException ioe = new IOException( 256 "unexpected content length header with 204 response"); 257 exc