test_response: ensure closed socket after write

We always close the socket immediately after a
successful write for two reasons:

  1) To prevent error responses from being rewritten.
     If we throw an exception in our request/app/response
     chain, we'll attempt to write an HTTP 400/500 response
     out if the socket is open.  No way to write to
     an open socket.

  2) To uncork the socket if TCP_CORK is enabled (Linux)
     ASAP.  This should be a tick faster than waiting
     to go back up the stack and close it there.

0 files changed, 0 insertions, 0 deletions