+1, it is a good habit to read off the data before closing the
connection. Otherwise this may lead to "connection reset " exception
sometimes.
-Felix
On 2016/12/12 13:07, Xuelei Fan wrote:
Hi John,
It's a good catch of the problem. Looks like the server side should
read the HTTP request at
Hi John,
It's a good catch of the problem. Looks like the server side should
read the HTTP request at first, and then write the HTTP response.
That's the server call:
InputStream sslIS = socket.getInputStream();
sslIS.read();
and then write the "HTTP/1.1, ...".
Thanks,
Xuelei
On 1
It's OK to me.
Thanks,
Xuelei
On 12/11/2016 7:21 PM, joe darcy wrote:
Hello,
Until JDK-8171061 is fixed, the test
sun/net/www/protocol/https/HttpsClient/ServerIdentityTest.java
should be problem listed on windows.
Patch below.
Thanks,
-Joe
diff -r b9cdffb87bea test/ProblemList.txt
--
Hello,
Until JDK-8171061 is fixed, the test
sun/net/www/protocol/https/HttpsClient/ServerIdentityTest.java
should be problem listed on windows.
Patch below.
Thanks,
-Joe
diff -r b9cdffb87bea test/ProblemList.txt
--- a/test/ProblemList.txtWed Dec 07 10:55:13 2016 -0500
+++ b/test/Pro
Please take a review at the release note at
https://bugs.openjdk.java.net/browse/JDK-8157389
Thanks
Max
Hi,
Please review this patch for test
sun/net/www/protocol/https/HttpsClient/ServerIdentityTest.java
Before the client get the response, the server may close.
Webrev: http://cr.openjdk.java.net/~jjiang/8171043/webrev.00/
Issue: https://bugs.openjdk.java.net/browse/JDK-8171043
Best regards,
Joh
