3aa81e8ba1
If the connection is closed right after the response was sent then it's wise to add 'Connection: close' header to the response so that the client optimizes its behaviour: e.g. does not reuse the socket for further http requests. Normally a client should retry a request if the reuse of an old socket fails and that should solve the problem but still this is an overhead. Signed-off-by: Gabriel Masei <gabriel.masei@1and1.ro> Change-Id: I29f1498610c567024def3beb1ad7014f2c15a232 |
||
---|---|---|
.. | ||
Buffer.hpp | ||
clientnb.cpp | ||
DelaySocket.cpp | ||
DelaySocket.hpp | ||
FakeSocket.cpp | ||
FakeSocket.hpp | ||
HttpHelper.cpp | ||
HttpHelper.hpp | ||
HttpRequest.cpp | ||
HttpRequest.hpp | ||
NetUtil.cpp | ||
NetUtil.hpp | ||
ServerSocket.hpp | ||
Socket.cpp | ||
Socket.hpp | ||
Ssl.cpp | ||
Ssl.hpp | ||
SslSocket.hpp | ||
WebSocketHandler.hpp | ||
WebSocketSession.hpp |