All geek questions in one place

Keep-alive for long-term HTTP session (non-persistent HTTP)

At work, we have a client-server system in which clients send requests to the web server via HTTP. Processing on the server side can sometimes take more than 60 seconds, which is the proxy server timeout value set by our IT staff and cannot be changed. Is there a way to keep an HTTP connection alive for longer than 60 seconds (preferably for an arbitrarily long period of time), or using pulsating messages from a server or client?

I know that there are persistent HTTP 1.1 connections, but this is not what I want.

Does the HTTP function have a health function, or should it be done at the TCP level through any socket option?

+3
source share
3 answers

Assuming that you control both sides of the system, you can fake it by periodically sending data back and forth so that the session does not work - most browsers do not disconnect while the data is moving.

, , , , ( Ajax), , . Ajax , , . - ( -), .

+1

.

+3

no-op - HTML, - :

<!-- keepalive -->

10 .

0

Source: https://habr.com/ru/post/1739545/

More articles:


All Articles