Re: Question about com.sun.net.httpserver.HttpExchange#sendResponseHeaders

Hi Wenbo, On 06/02/2019 23:21, Wenbo Zhu wrote: Thanks! The text looks good. p.s. is there a way I could get notified of any future updates on this issue? I had thought that I have a java.net account ... If you have the OpenJDK author status you should have the ability to l

Re: Question about com.sun.net.httpserver.HttpExchange#sendResponseHeaders

Hi Wenbo, This looks like a reasonable request. Since we are in agreement on the spec, I have logged https://bugs.openjdk.java.net/browse/JDK-8218554 to track it. The issue has a link to this mail thread for reference. best regards, -- daniel On 02/02/2019 00:27, Wenbo Zhu wrote: On Fri, Fe

Re: Question about com.sun.net.httpserver.HttpExchange#sendResponseHeaders

Hi Wembo, On 01/02/19 19:50, Wenbo Zhu wrote: 1) clarify in the API javadoc that chunked encoding is always applied even with Connection: close Chunked encoding is always applied if 0 is passed to sendResponseHeaders (this is a bit counter-intuitive, but 0 means chunked coding and -1 means Con

Re: Question about com.sun.net.httpserver.HttpExchange#sendResponseHeaders

Hi Wembo, On 31/01/2019 23:56, Wenbo Zhu wrote: Per the HTTP spec, chunked encoding may not be needed if "Connection: close" is set and the TCP connection will be closed (FIN) to complete the response body. Are you referring to HTTP/1.0? https://tools.ietf.org/html/rfc1945#section-7.2.2 I am

Question about com.sun.net.httpserver.HttpExchange#sendResponseHeaders

Per the HTTP spec, chunked encoding may not be needed if "Connection: close" is set and the TCP connection will be closed (FIN) to complete the response body. I am yet to write a test for this but the javadoc needs to address this behavior.. This behavior can be supported using the existing API,