How to disable keep-alive in the browser? Problem with Yota

Question

Google Chrome

Hello.

I'm telling a little story. In general, there is a web server. Everything is set up for us as it should, keep-alive is activated as it should be for 50 seconds and 100 transmissions.

There is a problem. For some reason, when working with Yota, keep-alive works buggy, because during idle time the physical connection is broken, while the browser thinks that everything is fine (the logical connection itself remains - TCP is open).

All this makes it very difficult to use the site with Yota, because the site seems to disappear from the network, although in reality everything is fine. After the decision was made to disable keep-alive, everything worked as expected, although we understood the risk of additional load. Nginx saves well, well done! I advise everyone.

Question after a long prelude.
How to force disable keep-alive on the browser side? We want to make a decision to enable keep-alive for all users, and for certain corporate clients to make a separate setting right in the browser, they simply cannot change such a miserable Internet as you understand. For other users, this is not a problem, since it is assumed that only perverts will use providers such as Yota, or eventually no one will use it.

Thank you for your attention.

UPD: I was contacted by a Yota employee, they conducted tests, they said they would resolve the issue.

Answer 1

For
Firefox browser about:config
network.http.keep-alive;false
network.http.proxy.keep-alive;false
or
For known client
Header: Connection: close

Answer 2

So that's what it's all about, and I broke my head what the hell is going on with the sponsored forum. Let's say you need to clean the topic from the flood, I open links to delete in new tabs (you need to confirm), sometimes it turns out 10-15 tabs or even more. And when you automatically go through the tabs and click the “delete” button, the site does not respond exactly every two tabs, although there is a connection. I was thinking that this is how Iota is trying to squeeze out the dough to stimulate the use of more expensive tariffs. I rarely need a fast fat channel, I'm sitting on 512 kb. I turned off the keepalive in the fox, it seems to work.

Answer 3

Try to enable SO_KEEPALIVE on the listening socket ( so_keepalivedirective parameter in nginx listen) with some aggressive values.
Documentation: nginx.org/r/listen/ru
Who knows, maybe constantly traveling ACKs will keep the connection alive.

Answer 4

I have such a problem with Google services (except mail). Is there any way to do this in the browser?