HTTP Keep-alive, sockets, and Poco::HTTPClientSession question

[vin-d]

Hi, I have a question about usage of different HTTP sessions that would reuse the same underlying socket (when each session is done) by the usage of the keep-alive flag.

The idea is to avoid the connection / disconnection handshakes and to have a socketpool available for sessions.

Is that something which can be done by the following events :

1. connect mySocket
2. creating my first HTTPClientSession
3. assign the attachSocket(mySocket)
4. do my HTTP GET/POST/etc... Read and Write as needed
5. detachSocket() and DrainBuffer()
6. delete my first HTTPClientSession
7. like in 2) create another HTTPClientSession
8. like in 3)
   etc...
   at the stop of the software close mySocket.

Is this something doable with Poco (or even permitted by the HTTP standards) ? i'm not very familiar with the HTTP protocol. If yes, should keep-alive be used in every HTTP exchange for this to work.

Thank you for your thoughts.

[github-actions[bot]]

This issue is stale because it has been open for 365 days with no activity.

[lb9726]

std::shared_ptrPoco::Net::HTTPClientSession
HttpClientPocoImpl::getHttpSession(const std::string &urlApi) {
Poco::URI url(urlApi);
static std::unordered_map<std::string, std::shared_ptrPoco::Net::HTTPClientSession> gMapSession;
static std::mutex gMutexHashSession;
std::lock_guardstd::mutex lock(gMutexHashSession);
if (gMapSession.find(urlApi) == gMapSession.end()) {
auto session = std::make_sharedPoco::Net::HTTPClientSession(
url.getHost(), url.getPort());
session->setKeepAlive(true);
gMapSession[urlApi] = session;
}
return gMapSession[urlApi];
}
I wrote a simple example using the above code, attempting to use the same session and set the keep alive flag. However, when I sent a message to the server using the same session, I saw that I did not reuse the previous link but instead re shook hands three times
Thank you for your thoughts.