https://bz.apache.org/bugzilla/show_bug.cgi?id=58583
--- Comment #3 from Rainer Jung <[email protected]> --- Supporting the OPs request: RFC 7230 also says: 6.6. Tear-down ... A client that sends a "close" connection option MUST NOT send further requests on that connection (after the one containing "close") and MUST close the connection after reading the final response message corresponding to this request. In this case here, the the requests to the first and the second server contains the client side "Connection: close", but only the first server responds with "Connection: close". The second does not, but both close the connection. Although it is not nice from the second server to not send "Connection: close", it is allowed (same RFC section: "The server SHOULD send a "close" connection option in its final response on that connection."). Looking at HTTPHC3Impl and HTTPHC4Impl it really seems we only set the "Connection: close" header but don't tell the HTTP clent to actually close the connection. I didn't check for the Java impl. So there really seems to be a bug here. -- You are receiving this mail because: You are the assignee for the bug.
