vlsi commented on issue #6330: URL: https://github.com/apache/jmeter/issues/6330#issuecomment-2619709747
> because this means the server is trying to shut down the socket, but the client didn't do it yet First, if the server was about to close the connection it should probably send `Connection: close` header, so the client knows the server does not want reusing the connection. Second, I'm afraid the only way to tell if "server" closed a connection is to read/write something to the connection. That means if the server silently closes a connection (which is (un)fortunately allowed by various HTTP RFCs). Frankly, it is not clear what clients are supposed to do with all this. It is not clear how Java implementation handles "silent connection close" >I think this is a bad implementation in the HttpClient4 library. It should simply remove a connection once the server requests it. Looks so, however, as the only way to detect "server-side closure" is to write data, so HttpClient4 should detect "IOException when writing headers", and retry the request. It looks like https://www.rfc-editor.org/rfc/rfc2616.html#section-8.2.4 specifies that, however, I'm not sure if that is the currently active RFC. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
