You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
I Use QNetworkAccessManager / QNetworkRequest / QNetworkReply to post a get on a subscriber channel.
By default, the connection is keep alive, but the info message does not change even if I set Connection: close in the header (and in that case, I unexpectedly still receive updates on the channel).
When I decide to quit the application, I close the initial request. From nginx point of view, I am closing a keep alive request prematurely, indeed before receiving one "last" message that finishes the initial request.
I can't find a proper solution to the issue, maybe You have a suggestion.
Hello.
I Use QNetworkAccessManager / QNetworkRequest / QNetworkReply to post a get on a subscriber channel.
By default, the connection is keep alive, but the info message does not change even if I set Connection: close in the header (and in that case, I unexpectedly still receive updates on the channel).
When I decide to quit the application, I close the initial request. From nginx point of view, I am closing a keep alive request prematurely, indeed before receiving one "last" message that finishes the initial request.
I can't find a proper solution to the issue, maybe You have a suggestion.
Sniffing the traffic:
and also the communication close handshake seems to be fine:
NGINX logs:
Kind regards.
The text was updated successfully, but these errors were encountered: